Achieving agility : How? , lesson learned captured

409 views
296 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
409
On SlideShare
0
From Embeds
0
Number of Embeds
75
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Achieving agility : How? , lesson learned captured

  1. 1. Organizational Agility Chandan Lal Patary patarychandan@gmail.com
  2. 2. How can Organization Bring Agility into the system?
  3. 3. Agility Influencing Factors? Customer Involvement Retrospect Team members are dedicated Top management support Time to market Infrastructure Test driven development and automation Continuous sharing and learning Refactoring and impediment removal
  4. 4. Agility Comes From Excellent Team Work
  5. 5. Heavyweight process vs Lean ? For Agility
  6. 6. Adaptability
  7. 7. Why we want to become agile? What kind of agility we are targeting? Below are the few Can we push the new product into market as fast as we can? (Cycle time reduction) Improved Employee and Customer satisfaction by delivering right, quality product? Reduce development cost?  Increase the percentage of defects detected in testing before production release
  8. 8. Path to achieve agility Continuous delivery Value generation, Early or frequent deliveries Measuring progress via deliverables Optimizing the work continuously Customer satisfaction
  9. 9. Ways to achieve Agility : Cockburn's (2001) :1) effective, 2) steerable, 3) rulebased, 4) (about) people, and 5) communication Anderson (2003):1) speed Larman (2003): responsiveness 1) speed 2) flexibility and 3) Schuh (2004): 1) speed, 2) people, 3) empowerment, 4) change, 5) feedback, and 6) value. Lyytinen (2006): 1) feedback, 2) adaptability, and 3) collaboration.
  10. 10. Ways to achieve Agility Subramaniam (2005):1) feedback, 2) adaptability, and 3) collaboration. Ambler (2007) : 1) iterative, 2) incremental, 3) self-organizing, 4) less process-driven, 5) collaborative, 6) cost-conscious, 7) (about) speed, and 8) customer-driven IEEE (2007): 1) iterative and 2) responsive
  11. 11. 4P Principle: lean transformations
  12. 12. Deliver as Fast as Possible • Production to market release time has to shrink • Much waste can be attributed to people waiting for constrained resources.
  13. 13. Agile transformation • Transformation for agility
  14. 14. Competency landscape  Automation – scripting and coding  Use Open source  Automation tools  System view  Technical excellence Skill , Competency, Knowledge
  15. 15. DevOps and Agility
  16. 16. Doctor say more frequent meal good for Digestion !
  17. 17. Self Organizing team  Dependency reduced from management  Ownership of responsibility) the work(Accountibility and  Decision making from bottom ( minimize approval)  Flat organization, no hierarchy  Team sprit, common goal , passionate , trust, transparency  Collaboration, Communication ,commitment
  18. 18. Seven waste of Software Development  Partially done work  Extra processes (or extra steps)  Extra (unwanted) features  Time involved with task switching  Time spent waiting  Tracking down information or needing approvals  Time spent correcting defects
  19. 19. Movie “300 “  Small and highly competent team members  Power of a patriotic army defending native soil  Symbol of courage against overwhelming odds  Self motivated and self driven team members
  20. 20. Think Small  Small Team  Small release  Small design  Small documentation
  21. 21. Discover the agility factor…..

×