Agile adds value

317 views

Published on

Value added by Agile PM in software development

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

  • Be the first to like this

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

No notes for slide

Agile adds value

  1. 1. Agile
  2. 2. Points •Software Development Methodologies • Pros and Cons • Deep dive • Value Proposition
  3. 3. Software Development Methodologies • Waterfall • Agile  Scrum  XP  Kanban
  4. 4. Waterfall workflow Gather Requirement Create Design Develop Product Test Deliverables Deploy Product Maintenance
  5. 5. Waterfall workflow Real World Scenario Gather Requirement Create Design Develop Product Test Deliverables Deploy Product Maintenance Change Re-done Takes too long Gets skipped Delayed Expensive
  6. 6. Waterfall Usage • Stable Requirements • Sponsors can visualize clearly at conceptualization stage • Well documented deliverables • Constant market scenario • Product retains its relevance throughout SDLC
  7. 7. What is Agile? • Sponsors conceptualization evolves gradually • Iterative development • Requirement and Solutions evolve • Collaborative effort between self-organizing cross-functional members
  8. 8. Agile Manifesto Individuals & Interactions over Processes & Tools over Comprehensive Documentation Customer Collaboration over Contracts and Negotiation Responding to Change over Working Software Following a Plan
  9. 9. Agile Manifesto Embrace Change Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  10. 10. Agile Manifesto Frequent Delivery Deliver working software frequently, ranging from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  11. 11. Agile Manifesto Early Delivery Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  12. 12. Agile Manifesto Collaboration Business people and developers must work together daily throughout the project.
  13. 13. Agile Manifesto Motivated Individuals Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  14. 14. Agile Manifesto Conversation The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  15. 15. Agile Manifesto Working Software Working software is the primary measure of progress.
  16. 16. Agile Manifesto Sustainable Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  17. 17. Agile Manifesto Simplicity Simplicity--the art of maximizing the amount of work not done is essential.
  18. 18. Agile Manifesto Technical Excellence Continuous attention to technical excellence and good design enhances agility.
  19. 19. Agile Manifesto Self Organizing Teams The best architectures, requirements, and designs emerge from self-organizing teams.
  20. 20. Agile Manifesto Tune and Adjust At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  21. 21. Agile Shift What’s the approach?
  22. 22. Agile flavors
  23. 23. Scrum Most commonly used…
  24. 24. Scrum How to play?
  25. 25. Scrum What they mean? User story It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper note. E.g. As a sales manager, I want to search for my customers by their first and last names so I can communicate with them with ease. Velocity The total effort a team is capable of in a sprint. The number is derived by evaluating the story points completed from the last few sprint's stories/features. This is a guideline for the team and assists them in understanding how many stories they can do in a future sprint. Daily Scrum Each day during the sprint, a project team communication meeting occurs at the same location and same time every day for 15mins. Sprint planning meeting It is held at the beginning of the sprint cycle where team selects what work is to be done, Prepare the time-bound Sprint Backlog, Identify and communicate how much of the work is likely to be done during the current sprint. Burn down The sprint burn down chart is a publicly displayed chart showing pending work in the sprint backlog. It is updated every day. It gives a simple view of the sprint progress. It also provides quick visualizations for reference. Scrum Master The person responsible for the Scrum process, making sure it is used correctly and maximizing its benefits. He is not a member Scrum team(s). Product Owner The person responsible for maintaining the Product Backlog by representing the interests of the stakeholders, and ensuring the work done by Development Team adds value to end Product.
  26. 26. Why Agile? Reduced Cost Improved Business Value What’s in it for me? Project Success
  27. 27. Conclusion

×