Agile and Traditional Management

1,450 views
1,337 views

Published on

Agile and Traditional Management
- key differences
- where we can use agile and why

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

No Downloads
Views
Total views
1,450
On SlideShare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
38
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Agile and Traditional Management

  1. 1. Agile Methods Zuzi Sochova sochova.com @zuzuzka Introduction Session Agile and Traditional Management
  2. 2. What means Agile to you?
  3. 3. What means Agile to you? Agile is common sense so don’t be disappointed
  4. 4. What means Agile to you? Agile is philosophy based on people, collaboration and shared values Scrum, Kanban, XP,… are Processes
  5. 5. Different Agile Projects
  6. 6. Different Agile Projects Using agile principles I’ve been:Organizing and coaching many SW teams but as well Leading department of 100 people Implementing HR strategyCoaching the company business strategy Managing small startup company
  7. 7. Where Agile started?
  8. 8. Successful IT projects The agile process is the universal remedy for software development project failure. Software applications developed through the agile process have three times the success rate of the traditionalwaterfall method and a much lower percentage of time and cost overruns. according to the 2011 CHAOS Manifesto from the Standish Group.
  9. 9. Agile vs. Traditional Management
  10. 10. Agile ManifestoWe are uncovering better ways of developingsoftware by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  11. 11. Why is Agile different? Agile is about trust in people while Classical PM is often about how to control people
  12. 12. Why is Agile different? Agile is good for complex and empirical environments
  13. 13. Why is Agile different? Software development is not a predictable process. Building another house often is. The predictable process needs a plan and control to stick to the plan and maybe adjust it a little bit when needed. Empirical process needs good change management and creativity.
  14. 14. Agile Adoption
  15. 15. Agile is Change Management http://quotesbank.org
  16. 16. Fundamental Difference about the View on People and Teams http://photos3.flickr.com
  17. 17. Learning and continuous feedback http://www.questcorp.com
  18. 18. Experience your own way http://www.zdn.cz
  19. 19. Cooperation
  20. 20. Responsibilityhttp://larryhehn.com
  21. 21. Global priorities http://theemptiness.info
  22. 22. Common Story http://abc.blesk.cz
  23. 23. On-time, Fast, Flexible, Predictable
  24. 24. Agile and Lean Processes used as process to any development
  25. 25. Agile and Lean Processes Agile team follows an iterative process that is lightweight, highly collaborative, self organizing, and quality focused.
  26. 26. Agile and Lean Processes A lean process continuously strives to optimize value to the endcustomer, while minimizing waste that may be measured in terms of time, quality, and cost. 
  27. 27. Scrum Process - Basics
  28. 28. Work in Iterations
  29. 29. Team Collaboration
  30. 30. Communication and Self-organization
  31. 31. Scrum Process – Summary
  32. 32. Agile and PMBOK PMBOK describes what should be done during the management of a project. Agile methodologies describe how to do the things that should be done. The approaches defined in the PMBOK® Guide—Fourth Edition and in agile are compatible. Agile can be used together with the PMBOK® Guide http://www.pmi.org
  33. 33. Agile and PMI – Scrum example Initialization • Same Planning • Scrum–like process, iterative functionality planning, adjust scope according to the customer feedback • how we communicate, organize team, roles Execution • Every iteration customer demo Monitoring • Retrospective, Sprint review Closing • Same • Acceptance every iteration
  34. 34. SummaryAgile principles are generally used to any complex empirical projects: Incorporate change (process, product) Implement Short Iterations Endorse self-organization  High collaboration Transparent Communication Continuous Learning Quality Driven
  35. 35. SummaryAgile processes are used inside project management
  36. 36. Zuzana Šochová, zuzi@sochova.comAGILE & SCRUM TRAINER, CONSULTANT AND COACHPersonal web: http://sochova.comEnglish blog: http://tulming.com Czech blog: http://soch.cz/blogTravel blog: http://asmat.euTwitter: @zuzuzka

×