Agile project management with scrum
Download as PPTX, PDF0 likes396 views
Agile project management with scrum - An introduction to Agile and Scrum project management framework
Ad
More Related Content
What's hot (20)
Similar to Agile project management with scrum (20)
Ad
More from Rasan Samarasinghe (20)
Ad
Recently uploaded (20)
Agile project management with scrum
- 1. Agile Project Management with Scrum An introduction to Agile and Scrum project management framework
- 2. About Me • Rasan Samarasinghe • Associate Project Manager - Allion Technologies • 10 years in Software Engineering, Lecturing, Project Management and Coordination
- 3. Agile Project Management • A set of practices to improve the effectiveness • Adaptive planning, evolutionary development, early delivery, continual improvement, flexible response to changes are key qualities • Scrum, Kan-ban, Extreme Programming are popular Agile frameworks
- 5. Drawbacks of Waterfall Process • No working software is produced until end of the life cycle • High risk and uncertainty • Poor model for long and ongoing projects • Not suitable for the projects where requirements are not stable • Difficult to measure progress within stages • Cannot accommodate changing requirements • Adjusting scope during the life cycle is difficult • Integration is done as a “big-bang” at the very end
- 6. Challenges in Traditional Project Management
- 7. Why People Shift to Agile • Managing Uncertainty • Improved Quality • Focus on Business Value • Stakeholder Engagement • Transparency • Early and Predictable Delivery • Allows for Change • Predictable Costs and Schedule
- 8. Agile Manifesto by Kent Beck
- 9. Scrum An iterative and incremental Agile Software Development framework for managing software projects.
- 10. Scrum Principles
- 11. Scrum Process
- 12. Core Roles in Scrum
- 14. Product Backlog in Scrum The Product Backlog contains the wish list of all the User Stories that would make the product great.
- 15. User Story • In Scrum, features are known as User Stories • Written from the perspective of the end-user. • The Product Owner, representing the users and customers of the product, decides which User Stories make it into the Product Backlog.
- 16. Release Backlog The goal of Release Backlog is to deliver a subset of the Product Backlog After identifying which User Stories will go into a particular Release, they become part of a Release Backlog.
- 17. Estimations Then User Stories are prioritized by the Development Team, who also estimate the amount of time involved to complete each item.
- 18. Estimation Technique: Time A simple technique is to create estimating buckets where User Stories fall into a complexity bucket.
- 19. Estimation Technique: Story Points Estimate work in comparison to the complexity of a well known but simple component.
- 20. Sprint Backlog • Each Sprint takes a manageable chunk of the Release Backlog and gets it to a Ship-Ready state! • Usually, a sprint is 2-4 weeks long
- 21. Sprint Backlog At the end of each Sprint, you should have a fully tested product with all the features of the Sprint 100% complete.
- 22. Burndown Charts The slope of the graph or Burndown Velocity is the average rate of productivity for each day. The Burndown Chart provides a day-by-day measure of the amount of work that remains in a given Sprint or Release.
- 23. Burndown Charts Knowing whether the project is on time or not early in the schedule, can help teams make the proper adjustments necessary to get the project on track.
- 24. Daily Standup Meeting Short daily standup meetings (The Daily Scrum) ensure everything is on track and everyone has the tools they need.
- 25. Daily Standup Meeting Team members list the work they have completed since the last meeting, any obstacles in their way, and what they are going to do next.
- 26. Sprint Retrospective After each Sprint, a longer Retrospective meeting helps fine- tune the process.
- 27. Sprint Retrospective This is a time for each team member to reflect on what went right and areas of improvement
- 28. Scrum Project Management Software
- 29. More Knowledge on Scrum
- 30. Questions
- 31. Thank You