Agile Development for Beginners: Scrum Roles, Events and Artifacts in Your First Sprint

Project & Development

Agile Development for Beginners: Scrum Roles, Events and Artifacts in Your First Sprint

Anyone new to agile development or joining their first Scrum team uses this beginner template to learn the 3 roles, 5 events and 3 artifacts and to run a first two-week sprint. The whiteboard lays out what agile development means, the 5 steps of a two-week sprint, three frames for the 3 roles, three frames for the 3 artifacts, a table of the 5 events, four MoSCoW columns that pick what fits this sprint, and a KPT retrospective. The task board has five columns - Product Backlog, Sprint Backlog, In development, Waiting for review and Done - and starts with 4 parent tasks and 12 subtasks, from learning the terms to review and retrospective, all not started. Join a team without knowing how Scrum works and the vocabulary leaves you behind, so follow this board from top to bottom for one sprint and you will also know what to say in the daily scrum. Unlike a board for teams already running sprints, this one is about the terms and the first cycle.

0 Likes 0 Copies Author: WeProcess
agile development Scrum sprint development team beginner
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Agile Development for Beginners: Scrum Roles, Events and Artifacts in Your First Sprint
Sign up free and use this template

Whiteboard preview

1. What agile development is (build, ... 2. The two-week sprint flow (the dail... 3. Product Owner 4. Scrum Master 5. Developers 6. Product Backlog 7. Sprint Backlog 8. Increment 9. The 5 events at a glance Agile Development... How to use: (1) R... Definition of don... Roles and agreements Blockers and prob... Insights and impr... In one sentenceIn a short period of about two weeks, build something that works and show it,collect feedback and fix it. Then repeat. How it differs from the old waye.g. instead of settling every specification before you build,you decide the build order and work down it a little at a time. The order can change later. Why it helpse.g. you see the real thing every two weeks, so if the direction is wrongyou notice within two weeks. You only redo one sprint of work. 1. Sprint PlanningDay one of the sprint. Sort what to build in the two weeks with MoSCoW on board 2. Development (two weeks)Build only what you selected. Even when a new request arrives, as a rule it does not enter this sprint. e.g. work only on the 3 login items, 13 points. 3. Daily Scrum (15 minutes a day)Every day of those two weeks, 15 minutes at a fixed time. Each person says what they did yesterday, what they will do today and where they are stuck. It repeats daily alongside the development. e.g. standing up at 10 every morning. 4. Sprint ReviewThe last day. Show working software to stakeholders and collect feedback. Up to 2 hours. Show the screen, not the slides. e.g. click through the new login screen live. 5. RetrospectiveRight after the review. Look at the way you work rather than at what you built. Up to 1.5 hours. Decide the next single step with KPT on board The person who decides what gets built first Owns the order of the Product Backlog e.g. decides that login fixes come before everything else The person to ask whenever the content is unclear The person who watches that the way of working is kept Removes blockers and keeps each event inside its time box e.g. takes in an interrupt request and reschedules it Not there to give orders, and not necessarily a manager The people who build, including design, coding and testing What fits in two weeks is estimated by the developers themselves e.g. three people share out the Sprint Backlog Developer here is the name of a role, not a job title Everything you want to build, in the order it will be built Higher means sooner. The Product Owner sets the order e.g. login fixes / notification settings / admin search A list with no end. It may grow along the way Only what you agreed to build in these two weeks Chosen in planning, and nothing is added mid-sprint e.g. the 3 login items, 13 points in total It also shows who is holding what The working thing that exists at the end of the two weeks Anything that misses the definition of done (the conditions the team agreed on in advance for calling something finished) is not part of it e.g. the login fixes, tested and checked This is what you show in the Sprint Review What happens Who attends Time box Sprint SprintThe two-week box that holds the other four. The length never grows mid-way. The whole Scrum team(Product Owner, Scrum Master, Developers) Two weeksFixed, one month at most Planning Sprint PlanningPick what to build in the two weeks and create the Sprint Backlog. The whole Scrum team Up to 4 hoursMorning of day one Daily Scrum Daily ScrumSay what you did yesterday, what you do today and where you are stuck. Developers(the other two roles listen) 15 minutesSame time, same place, daily Review Sprint ReviewShow working software and collect feedback. The screen, not the slides. Scrum team plus stakeholders(requesters, users) Up to 2 hoursThe last day Retrospective Sprint RetrospectiveLook at the way you work rather than at what you built. The whole Scrum team Up to 1.5 hoursRight after the review 10. Pick what goe... Must (essential) Only what the sprint goal cannot be reached without.e.g. fixing the bug where the password reset email never arrives Should (important) Important, but the goal still holds if you leave it out this time.e.g. rewriting confusing error messages Could (if there is room) It goes into the sprint, but it is the first thing dropped if time runs short. The goal holds without it.e.g. swapping the logo on the login screen Won't (not this time) Agreed not to do. Do not delete it, keep it in the Product Backlog (board #6).e.g. notification settings and admin search move to a later sprint 11. Looking back ... Keep (what to continue) Fixing the daily scrum at 10 every morning got everyone in the room Saying blockers out loud on the spot cleared them within half a day Problem (what did not work) 5 of the 13 points we picked did not finish inside the two weeks We could not turn down mid-sprint requests, so the Sprint Backlog swelled Try (what to try next) Start the next sprint at 8 points and add more only if room is left The Scrum Master takes in every interrupt request first
100%

Drag to move, scroll to zoom

Task board contents

Product Backlog 16 items

Learn Scrum terms
Plan first sprint
Run daily scrum
Review and retro
List the 3 roles
Line up 5 events
Check 3 artifacts
Set dates and days
Fill the backlog
Pick 2 weeks only
Yesterday and today
Raise blockers now
Move cards on board
Show working demo
Feedback to backlog
Pick one KPT Try

Sprint Backlog 0 items

In development 0 items

Waiting for review 0 items

Done 0 items