Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Myopia


Published on

While working on Agile transformations, through multiple organisations, I have realized one common roadblock in achieving this vision; Managers. Read on to know why managers fear agile implementation

Published in: Software
  • Be the first to comment

  • Be the first to like this

Agile Myopia

  1. 1. 1 Why Managers Hesitate To Impliment Agile
  2. 2. I am Abhinav Sabharwal You can find me at 2
  3. 3. How Managers View Agile ● It's the senior & middle managers who need more motivation for this change than the teams themselves. ● Few managers feel that Agile will create a huge chaos in their well-organized teams. ● It is precived as just a way for a team member or vendor-partners to shy away from SLAs. ● Traditional managers just love the reward- punishment system and hold vendor-partners accountable by keeping on to SLAs 3
  4. 4. 4 Some of the Concerns are ● It can become very chaotic when teams are in the so-called agile way of working. ● Any business can come in with a change at any point in time and expect it to be implemented! ● There will be no documentation, how would we refer details later. ● No one takes ownership when things go wrong. There is merit in what concerns the managers have. At times all these can be true if Agile is not followed in true spirit.
  5. 5. 5 Chaotic Environment ● The intent of any agile methodology is not to be unplanned or chaotic, at all. ● We have to be very well planned. Planned for shorter spans, though. ● No one can disturb the sprint. It is locked till the sprint is over, ● There are minimal or no unpredictable events during the sprint. ● Techniques like the scrum of scrums and scaled agile release train keeps all items well organised.
  6. 6. Change At Any Stage ● The team listens to only one person, and that is their product owner. ● All requirements from any stakeholders have to go via team's product owner. ● This way it is more disciplined and better organised. ● It is a chance to validate actual need for the equirements 6
  7. 7. 7 No Documentation!! ● Story cards are better than pages and pages of documentation with not much face to face interaction. ● The development team does not wait for documentation. ● There is a lot of face to face communication and clarification happeing ● Documentation can happen in parallel to construction. ● Documentation is lean as per the business needs.
  8. 8. 8 No Ownership ● Reward and punishment system ends up wasting a lot of time productive time & results into a blame game and finding fault in people ● While working in an agile way, there is a sense of belongingness towards the common vision ● Product/application is nurtured by teams. That keeps ownership sitting with the entire team (not just one person). ● This becomes reason for keeping things running on the track.
  9. 9. Questions 9You can find me at