Agile Organizations

426 views

Published on

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

No Downloads
Views
Total views
426
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Agile Organizations

  1. 1. AGILE ORGANIZATIONS ATHER IMRAN NAWAZ MARCH 28, 2011 Fundamentals and Practices
  2. 2. Agility: the ability to think, move, adjust and draw conclusions quickly
  3. 3. Fundamental Ideas …  Knowledge Workers  Software Development is Creative, Uncertain, Complex and Artistic  Novelty, Creativity and Urgency
  4. 4. History  Industrial Practices  Software Development is different from Manufacturing  Practices and then Processes Evolved  ‘Evolution’ of Agile Framework
  5. 5. It is result of consolidation of experiences over the years Agile is Evolutionary, not Revolutionary
  6. 6. Dilbert or Drucker Organizations? OR
  7. 7. Linear, Sequential, Non-Iterative, Closed (Assembly line model) Waterfall Methodology
  8. 8. Being Agile is a mindset
  9. 9. Being Agile is a Culture
  10. 10. Blueprint of Agile Software Development Methodologies Agile Manifesto
  11. 11. Principles of Agile Framework
  12. 12. Customer Focus  Satisfy Customer via Early and Continuous Delivery of Valuable Software  Working on Highest Priority Items from Customer
  13. 13. Embrace Change  Accept Change as part of process, not outside of it
  14. 14. Deliver Frequently  Deliver Working Software Frequently and Incrementally  Frequency: 2 weeks to 4 weeks
  15. 15. Everyone Works Together  Developers, Testers, Technical Writers, Business People  All Work Together Daily!
  16. 16. Customer Involvement  Customers decide what the team works on. Deliver business value.
  17. 17. Self-Organized Teams  Teams determine how the deliverables should be met  Servant Leadership
  18. 18. People matter  Projects revolve around motivated individuals and healthy work environment  Collaborative
  19. 19. Face to Face Communication  Should be the Primary Means of Communication
  20. 20. Working Software  Primary measure of success
  21. 21. Sustainable Development  Rhythm  Work/Life Balance
  22. 22. Slices of Functionality!
  23. 23. Working Example Software: Website to Purchase Goods manufactured by a vendor  Register  Browse Catalog  Add to Cart  Pay
  24. 24. Working Example Focus  Customer Focus  Incremental Delivery  Working Software  Manage Change  Provide Review  Get Feedback Develop a complete slice of functionality that lets users register, browse, select and pay (with limited functionality set)
  25. 25. Technical Excellence  Continuous Attention to Technical Excellence
  26. 26. Visibility  Highly Transparent Teams  Status, Accomplishments all visible to entire Team, Stakeholders and Outsiders
  27. 27. Retrospective  Continually Evaluate Yourself!  Feedback key to Improvement
  28. 28. Slices of Functionality!
  29. 29. Agile Organizations
  30. 30. Facebook  Focus on People  Automated Tests  Continuous Integration  Daily/Weekly Release  Multi-stage Deployment  Accelerated Learning  Quality is everyone’s responsibility  People select their own Work and Projects http://www.limitedwipsociety.ch/en/cas e-study.html
  31. 31. Agile Transition  Agile practices since 1999  Bottom-up Transition  Teams independently adopted Scrum  Pull Approach rather than Push approach  Two-Pizza Teams
  32. 32. Myths about Agile  The Agile movement is not anti- methodology, in fact, many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never- maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment..
  33. 33. SAMI Index of Agile Adoption
  34. 34. Scrum
  35. 35. Agility is the Objective - Scrum is a means
  36. 36. Scrum – Components  Sprint – Development Cycle (typically 4 weeks)  Roles  Product Owner  ScrumMaster  Team  Artifacts  Product Backlog  Sprint Backlog  Meetings  Daily Scrum  Sprint Planning  Sprint Review  Sprint Retrospective
  37. 37. Scrum – Process Overview  Start with prioritized requirements (Product Backlog)  Team selects requirements to work on during the first Sprint (Sprint Planning Meeting)  Team defines specific tasks to complete the requirements (Sprint Backlog)  Team goes in a 30-day Development Cycle (Sprint)  Team meets daily to sync up and highlight issues (Daily Scrum Call)  Team develops, tests and documents the functionality being worked on  At the end of Sprint, team demo’s completed functionality to customers and stakeholders and gathers feedback (Sprint Review)  Team Analyzes its performance (Sprint Retrospective)  Product Owner reprioritizes the Product Backlog  Team goes through the process again (Sprint 2, Sprint 3, ……. Release)
  38. 38. Scrum Process
  39. 39. Sprint
  40. 40. Product Owner
  41. 41. Product Backlog
  42. 42. Sprint Backlog
  43. 43. Sprint Backlog
  44. 44. Iteration Burndown
  45. 45. Challenges in Adoption  Change of Mindset  It’s More than Just a Change of Terminology  Have to Adopt the Philosophy!
  46. 46. Can you use Scrum to manage your Final Year Projects?

×