I was recently reminded of this quote by Maya Angelou when I happened to watch Groundhog Day, a Hollywood movie that features a protagonist who is very unhappy with his life.
In the movie, Phil is the protagonist and a weather reporter whose life carries a routine which is exactly the same every day, aka, a time loop. He struggles as he tries to make sense of the events in his life that are strikingly the same – it is not only the work he does, and the people he works with that he sees every day. It is also the beggar on the street, the accidental insurance agent, the pothole he happens to step into, etc. He soon starts hating the environment, the town, the people and the celebrations around the Groundhog Day and finds himself cheating others, getting into one-night stands and reckless driving. He tries to get out of the time loop by committing suicide multiple times, nevertheless wakes up to the same day, repeating his routine.
Finally he comes out of the time loop by changing his attitude towards life – using the knowledge he has gathered during the time loop, of every individual in the locality - he goes out of his way to help others, learns the piano, shows his vulnerable side to his girlfriend and ultimately confesses his love to her.
IF YOU CANNOT CHANGE ANYTHING OUTSIDE OF YOU, CHANGE YOURSELF.
Popular posts from this blog
The Agile manifesto and the principles have been clearly called out, but many companies focus so much on getting the processes right, that they end up ignoring the people factor. Which means it is the same old story as traditional development (aka, waterfall). Yes, processes and tools are important, but, hey, aren’t people who are more important ? Aren’t people who have to put the processes and tools to good use ? Aren’t people who have to be good at relating to one another and the customer, to build great products and be satisfied at work ? Read more: https://www.linkedin.com/pulse/agile-techno-structural-od-intervention-vijaya-devi-s/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BEkfmoJkUQGqCSe%2FfpWyU9A%3D%3D
Agile (or Sprint) retrospective is a useful mechanism for the scrum teams to implement continuous improvement in their processes. The scrum master may facilitate the retrospective meeting to help the team identify processes that worked well and those that did not work so well. The team goes on to find ways to improve the processes and try them out in the next sprint. Retrospectives are very important for Agile teams to be successful because it brings in a continuous ‘inspect and adapt’ approach to the processes applied for making the product. The Process of retrospective While there are many techniques to conduct the retrospective meeting, the general process followed is to take the individual’s feedback, collate them and identify top priority items to be implemented in the next sprint. It is fundamentally a process to collect feedback and make corrections to the system. According to the General Systems Theory, a system has inputs, outputs, transformation processes that
Many people are aware of the ‘Autonomy-Mastery-Purpose’ triad concept promoted by Daniel Pink in his hugely popular book ‘Drive’. Pink says for jobs to be intrinsically motivating, people need to have autonomy (to make decisions over what they do and need), mastery (continuously learning and improving oneself) and purpose (a guiding principle that is beyond profit and self-interest). What many people may not be aware of is a closely related and equally interesting framework presented by Hackman and Oldham in the 1970s which is called the Job Characteristics Model (JCM). It describes 5 core characteristics of a job and how they lead to intrinsic motivation. Below is the model representation : The model describes 5 core dimensions of a job, 3 psychological states it achieves and the personal and work outcomes of such a job. The core dimensions are : Skill Variety, Task Identity, Task Significance, Autonomy and Feedback. The first three contribute towards experienced