vladimirs ivanovs creating children's book in 45 minutes thanks to scrum
DESCRIPTION
Creating a book is not a simple project however applying Agile principles to the process might make it much more easier to manage and give you better results. During the workshop we create a children's book by using Scrum techniques. Workshop requires active participation in teams of Scrum size, gives ability to have fun and engage creativity. You will get familiar with Product Backlog, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective. I have done interactive workshops on big congresses and conferences, Agile events, at company offices and business schools and these are always perceived very well, as there are always some people who prefer "learning by doing". Recently I was on "roadshow" with this workshop - Global Scrum Gathering 2014 in Berlin, then IPMA Project Management congress 2014 in Rotterdam, and also Agile tour 2014 at Vilnius. Doing a game together with a training is an ideal combo (highly recommended), but be ready to adjust the schedule, add more space to reflections and discussions. If you want a PowerPoint with technical slides (countdown timer) and handout instructions with predefined backlog of user stories, ask me via vladimir at ivanov.lvTRANSCRIPT
Workshop
«Creating
children
book in 45
minutes
thanks to
Scrum»
Vladimirs Ivanovs
ITSM.International
The Agile Manifesto – a statement of values
Process and tools Individuals and
interactions over
Following a plan Responding to
change over
Source: www.agilemanifesto.org
Comprehensive
documentation Working software over
Contract negotiation Customer
collaboration over
•Scrum is an agile process that allows us to focus
on delivering the highest business value in the
shortest time.
• It allows us to rapidly and repeatedly inspect actual
working software (every two weeks to one month).
•The business sets the priorities. Teams self-
organize to determine the best way to deliver the
highest priority features.
•Every two weeks to a month anyone can see real
working software and decide to release it as is or
continue to enhance it for another sprint.
Scrum in 100 words
Putting it all together
Game schedule
00:04 Reminder on Product Backlog,
Sprint Planning, Daily Scrum
00:08 Sprint Planning (decide how much to do)
00:09 Day 1 in Sprint 1 (work)
00:13 Daily Scrum in Sprint 1
(what did you do, what will you do, obstacles)
00:14 Day 2 in Sprint 1 (work)
Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts
Product backlog • The requirements
• A list of all desired work on the project
• Ideally expressed such that each item has value to the users or customers of the product
• Prioritized by the product owner
• Reprioritized at the start of each sprint
This is the
product backlog
Sprint planning meeting
Sprint prioritization
• Analyze and evaluate product
backlog
• Select sprint goal
Sprint planning
• Decide how to achieve sprint
goal (design)
• Create sprint backlog (tasks)
from product backlog items
(user stories / features)
• Estimate sprint backlog in
hours
Sprint
goal
Sprint
backlog
Business
conditions
Team
capacity
Product
backlog
Techno-
logy
Current
product
Sprint planning 1. Team selects items from the product backlog
they can commit to completing
2. Sprint backlog is created
• Tasks are identified and each is estimated (1-16 h)
• Collaboratively, not done alone by the ScrumMaster
3. High-level design is considered
As a vacation planner, I want to see photos of the hotels.
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)
The daily Scrum 1. Parameters
• Daily
• 15-minutes
• Stand-up
2. Not for problem solving
• Whole world is invited
• Only team members, ScrumMaster, Product Owner, can talk
3. Helps avoid other unnecessary meetings
Everyone answers 3 questions
NB! These are NOT status for the ScrumMaster!
They are commitments in front of peers.
What did you do yesterday? 1
What will you do today? 2
Is anything in your way? 3
Game schedule
00:04 Reminder on Product Backlog,
Sprint Planning, Daily Scrum
00:08 Sprint Planning (decide how much to do)
00:09 Day 1 in Sprint 1 (work)
00:13 Daily Scrum in Sprint 1
(what did you do, what will you do, obstacles)
00:14 Day 2 in Sprint 1 (work)
Game schedule cont’d 00:18 Reminder on Sprint Review
& Sprint Retrospective
00:22 Sprint Review/Demo by each team
(show the work)
00:26 Sprint Retrospective
(what went well, what to improve)
00:28 Sprint Planning (decide how much to do)
•Product owner
•ScrumMaster
•Team
Roles
Scrum framework
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Ceremonies
The sprint review 1. Team presents what it accomplished
during the sprint
2. Typically takes the form of a demo of new features or underlying architecture
3. Informal
• 2-hour prep time rule
• No slides
4. Whole team participates
5. Invite the world
Sprint retrospective 1. Periodically take a look at what is and is
not working
2. Typically 15–30 minutes
3. Done after every sprint
4. Whole team participates
• ScrumMaster
• Product owner
• Team
• Possibly customers and others
Start / Stop / Continue Whole team gathers and discusses what they’d like to:
Start doing
Stop doing
Continue doing This is just one of many ways to do a sprint retrospective.
Game schedule cont’d 00:18 Reminder on Sprint Review
& Sprint Retrospective
00:22 Sprint Review/Demo by each team
(show the work)
00:26 Sprint Retrospective
(what went well, what to improve)
00:28 Sprint Planning (decide how much to do)
Game schedule cont’d 00:29 Day 1 in Sprint 2 (work)
00:33 Daily Scrum in Sprint 2
00:34 Day 2 in Sprint 2 (work)
00:38 Sprint Review/Demo by each team
(show the work)
00:42 Sprint Retrospective
00:44 Wrap Up
Credits 1. My son Arthur and daughter Nika:
They always check created books when I come back home
2. Mike Cohn, Mark Levison and Paul Heidema
3. www.mountaingoatsoftware.com/scrum
4. http://www.m62.net/powerpoint-slides/conference-slides/powerpoint-
countdown-timer/
5. http://www.xqa.com.ar/visualmanagement/wp-
content/uploads/standup2.jpg
Contacts
ITSM.international
linkedin.com/in/vivanov
+371 29160633
v.ivanovs
@vivanovs (Vladimir_ITSM)