4. An chef would...
Come up with some awesome recipes.
Write a shopping list
Do the shopping
Put it in the fridge
Prep your meals.
Get cookin’
Serve your meals.
Do a ‘Masterchef’.
5. Come up with some tasty recipes.
Taste is always the main goal.
... but you don’t know what it tastes like yet.
Some people hate cheese.
6. Write a shopping list
You roughly know what you want
You don’t make too many choices before you go shopping
7. Do the shopping
You go down your list
You decide which ingredients to get
How many calories?
You expect a certain quality
8. Put it in the fridge
It’s time to organise all that stuff you got.
Best before dates.
Utilise your cupboards, fridge and freezer.
9. Prep your meals
You get all your necessary ingredients together.
You might be making more than one course at once.
Delegate the tasks to the other chefs.
Everyone has their own chopping board.
10. Get cookin’
The fun bit for the chefs.
We know how long it should be taking
Pass it on if you need to.
Do some taste-tests as you go along.
11. Serve your meals
Presentation is key
Make sure it’s cooked all the way through
One course at a time.
There’s (normally) room for dessert.
Don’t speak with your mouth full!
12. Do a ‘Masterchef’
So, everyone has had a taste.
Let’s decide what was good, and what was bad.
13. An agile team would...
Come up with some amazing ideas
Write some user stories
Develop your user stories
Transfer to the backlog
Prepare the sprint
Get coding
Demo your product
Have a Retrospective meeting
14. Come up with some amazing ideas.
It always starts with the idea...
... but it’s only an idea at this point.
Changing over time
Setting your audience boundaries early
15. Write some user stories
Write as many user stories down as you can
Focus on the story narratives, rather than the criteria.
17. Story Narrative
As a provider search user..
I want to search for providers by speciality...
so that I can efficiently refer patients to specialists.
19. Develop your stories
Discuss each story with your team
Write acceptance criteria for each story
Make sure you mutually agree the ‘definition of done’
Watch out for ‘Epics’.
Estimate each story
Prioritise your stories
21. Acceptance Criteria
Given the user is on either the homepage or results page
When the users clicks “Search”
Then the they are given a list of providers.
23. Transfer to the backlog
You’ve written your detailed user stories
It’s time to transfer these to the appropriate places.
Use the backlog for most things...
... but the “Icebox” is useful for stories that can wait.
First indication of the project length
24. Prepare the sprint
Sprints begin with a meeting
Sprints usually last 2 weeks
Make sure all user stories have an owner
The team can view their tasks for the sprint
Make sure clients have agreed
25. Get coding
The fun bit for developers
We know how long to spend on stories
Collaboration
Test-Driven Development
26. Demo your product
Demo the latest features to the product owner.
Only include fully working features
Run through 1 each feature at a time.
End on a high
Wait to give your full opinion
28. The Releases
It’s different to Masterchef.
It’s more like releasing a recipe book.
Only when the product is usable and has sufficient features
Users will make it their own. Everyone has different tastes.
29. Daily Scrums
In the morning, we should have a meeting
We need to stand-up. (Sometimes called “stand-ups”)
Only 1 person talks at once (using a prop?)
We need to discuss:
What we’ve been up to
What we’re about to do
And what/who we need to achieve that.
31. Client Participation
Expected to participate in:
Prioritising features, for implementation order
Sprint planning meetings
Acceptance criteria
Retrospectives
32. Contract Definition
Things to ensure are defined in the contract:
Total value of the contract
Rates for times & material billing
Scope of the contract
33. Money for nothing
Client may terminate at the end of a sprint
Would pay 20% of the remaining contract value
What can we commit to?
Client must participate!
Resort to T&M billing
34. Change for free
If client is participating...
they can make changes to the scope
... as long as stories of equal scope are removed from the
contract.
