A review of Scrum and Kanban.
Agile, Agile, Agile!
Kevin Lawver :: http://kevinlawver.com
• Individuals and interactions over processes
• Working software over comprehensive
• Customer collaboration over contract
• Responding to change over following a plan
• Frequent releases
• Welcome changing
• All disciplines work
together in shorter
• Build projects around
• Face to face
• Sustainable pace and
• Maximize the amount of
work not done.
• Regular retrospectives
and process changes to
• Turns product development into a sustainable
• Achieve constant incremental improvement
that’s actually measurable!
• Lots of metrics about development progress
and lots of participation from stakeholders
But how do I do it?
Pick a Process: Scrum
• The Backlog
• The Sprint
• The Standup Meeting
• The Retrospective
• The Scrum Master
• Business “Owner”
How It Fits Together
Let’s go through a
• Whenever I say Scrum Master, think Project
• Whenever I say Business Owner, think,
ummm... Business Owner. They could also be
the Product Manager.
The Backlog is owned
by the Business Owner
& contains the building
A single requirement, documented
thoroughly enough that an “average”
person would understand it and be able
to implement it in a single sprint.
So that users can more easily buy songs, we need
to have a buy button on all songs that adds the
song to their shopping cart.
User Stories Should:
• Be simple
• Be focused on a single feature
• Have a single beneﬁt and action
Once a story’s been
• It’s put in the backlog in priority order
(priority is determined by the Business
• Someone goes in and adds tasks to the story
and then estimates how long those tasks will
take, preferably the person who will be doing
Related user stories can
be bundled into “epics”.
• A prioritized backlog with tasked-out and
estimated user stories.
• Everyone from the team available for the
• Everyone needs to know how many hours
they have available for that sprint.
• Go through prioritized and estimated user
stories and add them to the sprint.
• When everyone’s sprint is full, you’re done!
The Standup Meeting
• Takes place at the same time every day.
• Everyone on the team goes around and
answers three questions:
• What did I do yesterday?
• What will I do today?
• Where am I stuck and need help?
• Should take no more than 15-20 minutes
• Any discussions take place “ofﬂine” after the
• Everyone stands (keeps the chit-chat down)
• No one’s stuck for very long.
• No need for status reports, you get one
• Everyone is informed about what’s going.
• Projects are usually never late or “in crisis”
because problems are caught early.
When things go wrong...
There’s a process for
• A user story of equal or greater size gets
removed from the sprint and the new “ﬁre
drill” gets added.
• If the change is too big, the Sprint is “called”
and you go through Sprint Planning again.
At the end of the sprint,
sit down with
stakeholders and review
It’s the ﬁnal “go/no go”
decision for the work in
This is my favorite part!
Answer the following:
• What went well?
• What didn’t go well?
• What can we do better next time?
• We create a document that everyone can ﬁll
out beforehand. Works really well for
• Set a time limit (1 hour)
• Don’t let it become a bitch session - it should
be constructive (responsibility vs. blame).
Rinse & Repeat
Favorite Things About
• Team history
• Constant incremental improvement
• Sustainable development
• Built-in process for handing ﬁre drills
• Business owners have frequent check-ins and
everyone feels involved and sees progress.
Questions before we
jump into Kanban?
It’s basically Scrum
without Sprint Planning
It was invented by
Toyota for their
And is Japanese for “just
• The backlog still exists and is still prioritized.
• Everything happens on “the board”
• When a resource is available, they take the
next task from the backlog that they can
• Less work for the Scrum Master
• More ﬂuid and easier to see where
everything is on the board.
• No beginning or end, just endless tasks.
• Fewer artifacts and metrics than Scrum in my
• Processes are made to be adapted
• The most valuable pieces to me are the Daily
Standup and Retrospectives
• Agile is basically Project Management evolved
and can be applied to almost any kind of
• [email protected]
• Kanban Board photo from Mark Derricutt: