scrum.pptx

Scrum Roles • Product owner: The person responsible for the business value of the project and for deciding what work to do and in what order, as documented in the product backlog. • ScrumMaster: The person who ensures that the team is productive, facilitates the daily Scrum, enables close cooperatio...

Scrum Roles • Product owner: The person responsible for the business value of the project and for deciding what work to do and in what order, as documented in the product backlog. • ScrumMaster: The person who ensures that the team is productive, facilitates the daily Scrum, enables close cooperation across all roles and functions, and removes barriers that prevent the team from being effective. • Scrum team or development team: A cross-functional team of five to nine people who organize themselves and the work to produce the desired results for each sprint, which normally lasts 2-4 weeks. Information Technology Project Management, Eighth 1 Scrum Artifacts • An artifact is a useful object created by people • Scrum artifacts include: • Product backlog: A list of features prioritized by business value • Sprint backlog: The highest-priority items from the product backlog to be completed within a sprint • Burndown chart: Shows the cumulative work remaining in a sprint on a day-by-day basis Information Technology Project Management, Eighth 2 Scrum Ceremonies • Sprint planning session: A meeting with the team to select a set of work from the product backlog to deliver during a sprint. • Daily Scrum: A short meeting for the development team to share progress and challenges and plan work for the day. • Sprint reviews: A meeting in which the team demonstrates to the product owner what it has completed during the sprint. • Sprint retrospectives: A meeting in which the team looks for ways to improve the product and the process based on a review of the actual performance of the development team. Information Technology Project Management, Eighth 3 Table 3-18. unique Scrum Activities by Process Group Information Technology Project Management, Eighth 4 Planning • Not different from PMBOK® Guide • Still create a scope statement and can use a Gantt chart for the entire project schedule; other planning similar (risk, etc.) • Different: • Descriptions of work are identified in the product and sprint backlogs, more detailed work documented in technical stories, estimate a velocity or capacity for each sprint; release roadmap often used for schedule Information Technology Project Management, Eighth 5 Executing • Not different from PMBOK® Guide • Still produce products, lead people, etc. • Different: • Produce several releases of software - users of the new software might be confused by getting several iterations of the product instead of just one • Communications different because the project team meets every morning, physically or virtually Information Technology Project Management, Eighth 6 Monitoring and Controlling • Not different from PMBOK® Guide • Still check actual work vs. planned work • Different • Names of key reviews are the daily Scrum and the sprint review • A sprint board is used instead of a tracking Gantt chart or other tools • Use a burndown chart vs. earned value chart Information Technology Project Management, Eighth 7 Closing • Not different from PMBOK® Guide • Focus is still on acceptance of deliverables and reflection • Different: • The retrospective is similar to a lessons-learned report, but it focuses on a shorter period of time. It is intended to answer two fundamental questions: • What went well during the last sprint that we should continue doing? • What could we do differently to improve the product or process? Information Technology Project Management, Eighth 8 

Show More Show Less