Sprint 0 Training
The Problem
Red Bucket Extermination Kaizen
Step 1
Go & See
Select Your Fighter
CTOness
Standardness
Select Your Fighter
Standardness
Not Saying
Amazingness
Select Your Fighter
Very
Warmheatingness
Step 1
Go & See
Fixify
- Sale : Sadiq
- 2 Half Days Starter Sold
- Tools : Whiteboard, Post its, Trello, Poker Planning
- Outcome : No project sold (for now...)
Content
- Methodology
- Success, hypothesis of success
- Epics Estimated
- Some User Stories Estimated (different scale)
Unit Media
- Sale : Fabrice
- 2 Half Days Starter Sold
- Tools : Trello, Excel
- Outcome : No project sold
Content
- Sponsor presentation
- Success
- User Testing
- Epics Estimated
TapIn
- Sale : Nicolas
- 2 Starters + Project Sold
- Tools : Whiteboard, Trello, Poker Planning
- Outcome : Sprint 1 Red Bucket
Content
- Methodology
- Success
- Epics created
- Epics spread in sprints
- First Sprint US created and estimated
Groupama
- Sale : Nicolas
- 3 Starters Sold
- Tools : Slides, Whiteboard, Trello, Poker Planning
- Outcome : ?
Content
- Methodology
- Success, Hypothesis of success
- Epics created and estimated
- Global Estimation of Project
Step 2
Kaizen
Tool : Client's Voice
Martine Cannon - TapIn PO
Lack of clarity about how project works and team works. Also architect much handsomer that rest of the tech team.
Methodology Unclear
- TapIn
- Unit Media
Commitment issues
- Multiposting
- MatchPint
?
- Fixify
Root Causes
Methodology Unclear
- Daily validation calls
- Theodo Scrum Guide
- Using French Starter Slides
Commitment issues
- Sales Call
Countermeasures
- Asking for feedback on clarity
- Theodo Project Form
Checks
- Translating/Adapting Starter Slides
- Training
- Blog Article on 3 parts Starter
Acts
Starter 0
Presentation
Why ?
- Making sure the project will succeed
- Making sure the 1st sprint will succeed
- Convincing sponsors
What ?
- Starter 1
- Technical Challenge + 5 Estimation
- Starter 2
- Starter 3 (Kick-Off)
Starter 1
Why?
- Onboard the client
- Define the success
Who?
- The sponsor
- The PO
- The architect
- The SM
- The Project Director
What?
- Describe the roles and the expected commitments
- Present the methodology, standards and indicators
- Define the business problem
- Define the success criteria
- Define the success hypothesis
- Define the Challenge User Story
- Write the Definition of Done
Technical Challenge
Why?
- Making sure team can bring value from day 1
Who?
- The architect
- The PO
- Possibly sponsors if needed
What?
Put a feature all the way to production
- Pick a simple US that includes the dependencies of the project. Make it a 5.
- Draw the process for getting it on production
- Estimate completion of each step, "unblocker" if identified and date to unblock
- Plan it before the Starter 2
5 Estimation
Why?
- Succeed sprint 1 by picking an reasonable speed
Who?
- 2-3 Architect Developers
What?
- List all technical tasks involved in doing the challenge user story
- List the context of the project (team, tech stack...)
- Each architect estimates how long each tasks should take
- Architects reveal their estimations and agree on time for each step
- Architects match the 5 with the total time needed
Starter 2
Who?
- Sponsor
- PO
- Architect
- SM
- Project Director
Why?
Provide global visibility on the project and the plan to reach the success
What?
- Create Epics
- Prioritize Epics
- Estimate Epics (compared to the 5)
- Draw the Global BDC
- Remove epics if needed until the project fits
Starter 3
Why?
Prepare the first sprint
Who?
The Scrum Team!
What?
- Split epics until you have 30 user stories to prepare sprint 1
- Estimate user stories
- The team plans a project install ticket
- The team commits on the sprint 1
- SM has PO fill in Theodo Project Form
FAQ
Does the 5 points ticket include the complexity of the setup?
No, the 5 points would be for that ticket in normal sprint mode with Theodo standards respected.
Should the architects doing the 5 Estimation include the complexity of the setup?
No, for similar reasons.
The 5 points was actually a lot harder because the architect faced a lot of dependencies during the challenge. Help?
If the dependencies are fixed before starter 2, it's a proper 5. If not, you have to reestimate it before estimating the epics.
We couldn't do the Estimation of 5 before the starter 2
During Starter 2, the tech team does it live but makes sure to mention it's not the standard process and that the result will be double checked with the other architects ASAP.
We couldn't do the technical challenge before the starter 2
Make sure to mention epics could take much bigger proportions after the technical challenge and estimations should be taken lightly.
The tech team just had the architect in starter 2 or 3
The best option is to spend more time on epics (estimation can be finished in starter 3). You can create Sprint 1 user stories but do not estimate them with just the architect.
Can we change the SM/Architect for starters/technical challenge/sprints?
NO!!!
We didn't manage to sell 3 starters
If you sold 2 starters and a project, you can just do starter 3 in the beginning of the project.
If you just sold 2 starters, go quicker, squeeze in user stories splitting and estimations for sprint 1 and provide Nolan's stuff to the PO.
We didn't manage to sell the technical challenge
Make sure you launch as many actions as possible if you foresee blocking issues before/during the starters.
Make sure to include both architect and dev time to setup the project in sprint 1.
Sprint 0 Training
By Woody Rousseau
Sprint 0 Training
- 701