add-memberalign-toparrow-leftarrow-rightbellblockcalendarcamerachatchevron-leftchevron-rightchevron-small-downchevron-upcircle-with-crosscomposecrossfacebookflagfolderglobegoogleimagesinstagramkeylocation-pinmedalmoremuplabelShape 3 + Rectangle 1pagepersonpluspollsImported LayersImported LayersImported LayersshieldstartwitterwinbackClosewinbackCompletewinbackDiscountyahoo

Scrum Club Scrum

Before You Begin
Make a master list of all the people to be involved. Sort into the following categories:
Scrum Master
Chickens (stakeholders)
Day-to-Day Operations
This section is about the process flow from the Sprint Planning Meeting to Closeout.
Week 1: Sprint Planning
Monday: Product Planning
Get all the pigs and chickens in the same room.
Decide on what the big picture goal is
Create a product roadmap of the major functions that need to be addressed.
Don't worry about planning perfectly
Tell them that on Wednesday they will need to sort the roadmap according to priority
Give everyone points with which to choose the most important feature
Tell them to prepare to vote for a Product Owner
Tell them to come back on Wednesday knowing which features they will vote for.
Tuesday: Chicken Negotiation
Let them have all of Tuesday to chit chat and informally come to an agreement
Wednesday: Chickens Choose What to do
Pigs put points on the features they most need
Put the features in order of need
Is this a good order of delivery? If yes, end the meeting. If no, choose the most feasible order of delivery. Remember that we are sorting the big chunks.
Hold vote for Product Owner (is now a pig)
Product Owner picks one core feature off the top for first delivery item.
Tell pigs to think about core item for Thursday. Talk to the chickens.

Thursday Meeting: How to do it
Make a list of all the things that go into delivering core item
Put each into order of ?I need x to do y?
Sort work into ?buckets? across three milestones:
Milestone for this sprint (alpha, beta, gamma)
Milestone for micro sprint (1.6.5, 1.6.6, 1.6.7)
Milestone Product Backlog
Choose meeting time and method that works for everyone
Friday: Catch Up on your Email and Paperwork
No, really. You want everyone in on Monday with a clean plate.
What Goes Wrong
Someone won't show for a planning meeting. Cancel the planning meeting. Talk to them offline and resolve.
Week 2: Sprint Starts
Monday: Kickoff meeting in the morning.
Present team with tasks for sprint. Each team member picks a task from the list.
Tuesday (and every day after): Hold a stand up meeting in the morning.
This is a 15 minute daily meeting. It should be painless. If someone starts going off track or a discussion is sparked, the person is asked to hold comments/questions until later. Each team member says:
What I did in the last day / week
What I will do today / this week
What are my roadblocks and what do I need?
If the person finished a task, they pick a task from the list. Let everyone go to work. Repeat the next day.
What Goes Wrong
If there is an obstacle that just stops that person, someone is immediately assigned to remove it.
If someone outside the team tries to poach a team member's time during the sprint, the CSM redirects. If it really is a fire, stop the sprint. The whole team is assigned to attack the root cause.
More work is discovered during course of sprint than initially discovered. If small and obtainable within the Sprint, keep it in that sprint. If it will slow down the sprint, stop the sprint and swarm on it. If it is not necessary to the sprint, put it in the product backlog.
Somebody missed a Pig or a Chicken. Talk to the person about what you are currently working on. See if you are missing any features. If something significant is missing, stop the sprint. If it can wait, add it to the Product Backlog.
End of Week 6, End of Sprint
Deliver finished work product.
Week 7-10, Micro Sprint
Clean up from Sprint. Take care of business. Hold the following two sessions in week 7 immediately following the Sprint.
Monday: Hold a Sprint review meeting
This is about PRODUCT. Invite the Product Owner and the Pigs.
What is good?
What is bad?
What do we need to fix?
Add all items to Product Backlog
Wednesday: Hold a Scrum review meeting
This is about PROCESS. Scrum Master, team only.
Review this guide.
What went right?
What went wrong?
Where did people depart from this process?
Identify lessons learned on a white board. Take a photo and save it.
When you are ready to do the next sprint, just return to the Sprint Planning Meeting instructions.

Table of Contents

Page title Most recent update Last edited by
Scrum Club Scrum April 2, 2008 12:29 PM Amanda
Project Management and Social Networking April 1, 2008 1:56 PM Amanda
Mindshare Cartoon: Scrum Entrepreneurship March 31, 2008 4:38 PM Amanda
Policy for advertising to members March 21, 2008 6:27 PM Amanda
About LA Agile & Scrum User Group April 1, 2008 1:51 PM Amanda

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy