achieving agility : how? , lesson learned captured
TRANSCRIPT
How can Organization Bring Agility into the system?
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
Agility Comes From Excellent Team Work
Heavyweight process vs Lean ? For Agility
Adaptability
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
Path to achieve agility
Continuous deliveryValue generation,Early or frequent deliveriesMeasuring progress via deliverablesOptimizing the work continuouslyCustomer satisfaction
Ways to achieve Agility :
Cockburn's (2001) :1) effective, 2) steerable, 3) rule-based, 4) (about) people, and 5) communication
Anderson (2003):1) speed
Larman (2003): 1) speed 2) flexibility and 3) responsiveness
Schuh (2004): 1) speed, 2) people, 3) empowerment, 4) change, 5) feedback, and 6) value.
Lyytinen (2006): 1) feedback, 2) adaptability, and 3)
collaboration.
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
4P Principle: lean transformations
Deliver as Fast as Possible
• Production to market release time has to shrink• Much waste can be attributed to people waiting for constrained resources.
Agile transformation
• Transformation for agility
Competency landscape Automation – scripting and coding Use Open source Automation tools System view Technical excellence
Skill , Competency, Knowledge
DevOps and Agility
Doctor say more frequent meal good for Digestion !
Self Organizing team Dependency reduced from management Ownership of the work(Accountibility and
responsibility) Decision making from bottom ( minimize
approval) Flat organization, no hierarchy Team sprit, common goal , passionate , trust,
transparency Collaboration, Communication ,commitment
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
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
Think Small Small Team Small release Small design Small documentation
Discover the agility factor…..