Meetings and Artifacts in Scrum

A presentation on some of the key meetings that are usually held by a Scrum meeting including the artifacts/work products from them.

Transcript

1. Meetings and Artifacts in Scrum Chencha Jacob jacob@chenchatech.com @jchex
2. Scrum Meetings
3. Sprint Planning • Attended by all team members • Used to decide the user stories to be done during the sprint • Estimation of time per user story usually carried out • The sprint goal is defined • Buy-in is required from the product owner and the development team
4. Daily standups • The heart beat of scrum • Held daily • Maximum 15 minutes • Everyone ideally is standing • Answer three questions ◦ What did you do yesterday? ◦ What will you do today? ◦ Do you have any blockers? • Fosters commitment and accountability
5. Client Demo • Time to show off all the hard work • Meeting involves client and team members • Kept informal • Client can freely interact with the working application
6. Retrospectives • Kaizen, the process of continuous improvement • Happen immediately after the sprint • Each team member decides what to ◦ Start doing that wasn’t being done ◦ Stop doing that was counterproductive ◦ Continue doing since team already doing quite well • Choice one or two improwments that can be made - and add them as tasks for the next sprint.
7. Scrum Artifacts
8. Backlog • A list of user stories to be implemented • Prioritized by client (owned by the PO), estimated by developers
9. User story • A short description of a feature to be developed • In physical boards, the story needs to be short enough to fit into an index card • Takes the format of ◦ As a ____ ◦ I want to ___ ◦ So that ____
10. Velocity • Provides a measure of how fast the team is delivering projects • Useful for future planning • Can point out when team is falling behind Velocity = No of features / Week
11. Burndown chart • Shows the amount of work remaining to completion • This can be the no of user stories or story points (estimates) for the stories • At the end of the sprint the chart is adjusted to show the remaining points
12. Wireframes • Low fidelity representation of the product • Useful for communicating product vision • Can usually be quickly sketched up • Can be iterated far more cheaply than full blown websites