Agile : A Techno-structural OD Intervention


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

Comments

Post a Comment

Popular posts from this blog

How to know if your Job is Intrinsically Motivating

Image
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
Read more

Designing Agile Teams Using Socio-Technical Systems

One of the core aspects of Scrum is self-organizing teams that deliver software in small iterations called sprints. For those that try to move from traditional development models to Agile, one of the major challenges is forming self-organizing teams. The sprint teams are truly cross-functional teams that choose the best way to do their work without being directed by others from outside. How does such a team differ from the project teams in the traditional models? Are there any design principles or theoretical frameworks that can help us go about forming such teams? Designing Agile Teams using Socio-technical Systems Theory One of the core aspects of Scrum is self-organizing teams that deliver software in small iterations called sprints. For those that try to move from traditional development models to Agile, one of the major challenges is forming self-organizing teams. The sprint teams are truly cross-functional teams that choose the best way to do their work without
Read more

Feedback Fundamentals

Image
  “You cannot improve what you don’t measure’" – Edward Deming If I have to slightly tweak Deming’s words, I would say “you cannot improve what you don’t get feedback on”. It is that time of the year when most of the organizations are working through their annual performance review rituals. Managers face a challenging task of giving a satisfactory review, rating and raise. What was once a purely annual performance review, has undergone some changes - many organizations conduct periodic – quarterly or half-yearly reviews to ease the process. Periodic review meetings help to avoid surprises and help individuals improve their performance on a continuous basis. Most importantly they help in improving the process of review itself. One of the fundamental processes in the performance appraisal cycle is the process of giving feedback – useful information for the receiver to help him/her to make the necessary corrections in behaviour so that performance improve
Read more