Agile scrum
0 likes165 views
The document provides an overview of the Agile Scrum methodology for project management. It describes the waterfall model and its limitations. Scrum is introduced as an Agile technique that uses short sprints, daily stand-ups, and retrospectives. Key roles in Scrum include the Product Owner, Scrum Master, and self-organizing team. The Scrum process involves storytelling, maintaining a product backlog, sprint planning, estimation, and delivering working software increments at the end of each sprint.
Agile scrum
- 1. Agile - Scrum Project Management Technique Session 1
- 3. The Waterfall Model T I M E
- 4. The Waterfall Model - GOOD Things This model is simple and easy to understand and use. It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. In this model phases are processed and completed one at a time. Phases do not overlap. Waterfall model works well for smaller projects where requirements are very well understood
- 5. The Waterfall Model- Problems
- 6. The Waterfall Model-Problems When application testing stage, difficult to go back and change something that was not well-thought out in the concept stage. No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for the projects where requirements are at a moderate to high risk of changing
- 7. Enter AGILE • Adaptive to Change • Customer satisfaction by rapid, continuous delivery of useful software. • People and interactions over process and tools. • Working software is delivered frequently. • Direct communication – narrows gaps • Close, cooperation between business people and developers • Even late changes in requirements are welcomed
- 9. Agile Project Management Techniques • Scrum • Kanban • XP – Extreme Programming • Crystal • Lean
- 10. Scrum for Organizations • Improved Delivery • Transparency • Responsiveness • Features Increased/decreased • Measurable
- 11. Scrum • Collaborative Effort – Promotes team work • Transparency – Knowledge Distribution • Sense of Contribution • Self empowered teams • Measurable
- 12. Scrum is Used by
- 13. Agile - Scrum Questions ??? THANK YOU
- 14. The SCRUM Process • One of the Agile methods for Project Execution • Most Popular – Widely Accepted • Easy to Understand
- 15. How Scrum Works
- 16. How Scrum Works
- 17. Roles in Scrum •Product Owner •Scrum Master •The Team
- 18. Roles in Scrum – Product Owner • Knows Business need • Creates and maintains the Product Backlog – can add/remove items • Knows the priority of the items • Sets ‘Acceptance Criteria’
- 19. Roles in Scrum – Scrum Master • The ‘Superman’ • Chooses Commit/Not commit on Stories • Facilitates Scrum Events • Facilitates Communication • Gets team consensus • Removes impediments
- 20. Roles in Scrum – The TEAM • Sizing 7+/-2 • Self Organized and empowered • Able to estimate • Raises Impediments • Pull the stories • Help each other
- 21. The SCRUM Process •Story Telling •Product Backlog •Backlog Grooming
- 23. The SCRUM Process •Sprinting on Work •Stand up Meetings
- 24. The SCRUM Process •Definition of ‘Done’ •End of Sprint – Demo •Retrospection
- 25. SCRUM – Definition of Done • Achieves Acceptance Criteria • Starts functioning immediately-workable • Can be based on various parameters • Can additionally have a checklist
- 26. SCRUM – Definition of Done • Examples : –No technical or functional errors –QA Testing passed –UAT Testing passed –Works on the Client’s testing server
- 27. Art of Story Telling •Requirement •Story v/s Epic •Not too large
- 28. Art of Story Telling - Examples • As <> I want to <> So that… • As <a system user> I want to <login to system> so that <I can use the system> • As <an administrator> I want to <view audit log reports> so that <I can track the system> • As <a customer> I want to <order a product from the website>
- 29. Product Backlog •List of Requirements •Epics •Business Value •Dynamically Resizable
- 30. Product Backlog
- 31. Product Backlog Grooming • Understand the story • Break down epics • Remove unnecessary things/ideas • Is done to get a rough idea on a story
- 32. Scrum Team Capacity •“Storypoints” •Measurement •Calculated for each team member •Based on previous experience /complexity of Tasks
- 33. Sprint Planning Meeting Team sits together • Product Owner • Scrum Master • Team • Other interested Stakeholders –Product Owner tells the story –Team Identify Priority –Identify Acceptance Criteria –Story points – Complexity
- 34. Sprint Planning Meeting • Assumption : some grooming has already being done • No good or bad questions • Break it up as much as could • Do not assume anything
- 35. Sprint Planning - MoSCoW MoSCoW method •Must have •Should have •Could have •Won’t have
- 36. Sprint Planning - How its done •Team has access to product backlog •Product Owner tells the story
- 37. Sprint Planning - How its done • Team asks questions to : –Identify Priority –Take notes about the story details –Breaks stories in to tasks –Puts estimates on the tasks –Either commits or does not commit the story
- 38. Sprint Planning - Estimation • Happens during or in later part of sprint planning meeting • Product Owner is optional • Goal is to –Identify Storypoints-required efforts –Come up with a WBS
- 39. Sprint Planning Meeting Inputs • Details of the Story • Rough Estimations • More detailed questions • Work effort Required Outputs • How Many Stories are committed • Priority on each story • Acceptance Criteria
- 40. SCRUM – Daily Stand ups • Duration : 15 minutes • Team gets together • Product owner is optional • Only 3 items –What did I worked on yesterday –What I am working today –Any impediments ? Blockers ? Showstoppers ?
- 41. SCRUM – Retrospections • Team gets together, Product owner is optional • Only 3 items –What went well during this sprint –What did not went well during this sprint –Plans to improve on next sprint
- 43. Scrum Board
- 44. SCRUM – Some Keywords • Sprint – timeframe of work in which the committed stories are being worked upon by the scrum team. • Capacity – team’s time allocation in terms for hour for any given sprint.
- 45. SCRUM – Some Keywords • Work ahead : Story may be planned for next sprint but team can work if they have Capacity • Impediment : A problem or an issue which stops somebody from continuing work
- 46. SCRUM – Some Keywords • Grooming – To understand the stories better in order to estimate them better. • Epic – Something too large or too unclear to estimate- More than a story