The document discusses agile frameworks like Scrum and Kanban. It provides an overview of their key principles and concepts, such as visualizing workflow, limiting work-in-progress, and continuously improving. The document compares Scrum and Kanban, noting that Scrum is generally better for project teams with planned work and high estimation ability, while Kanban works better for sustaining teams with demand-driven work and varied capabilities. It concludes by emphasizing the importance of inspecting and adapting practices over time.
9. 9
Steps
1. 1 minute prep time
2. Give an estimate
3. 1 minute iteration
4. 1 minute
improvement
& new estimate
5. Repeat steps 2-5
five times
Collaboration Exercise
GOAL: Earn as many
“ball points” as
possible in 1 min
Rules:
1. Balls must touch everyone
on the team
2. Balls must have “air time”
when being passed to each
person
3. Ball must end where it
starts
4. Balls that fall to the ground
do not count
Thank you Bachan Anand & Boris Gloger
27. Certainty
Agreement
When to use Empirical?Lean Principles
1. Eliminate waste
2. Amplify learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build integrity in
7. See the whole
29. Certainty
Agreement
High
When to use Empirical?Kanban concepts
1) Visualize Value Stream
2) Limit Work In Process (WIP)
Similar to Scrum
Time-boxing to limit work
30. Certainty
Agreement
High
When to use Empirical?Kanban concepts
1) Visualize Value Stream
2) Limit Work In Process (WIP)
Similar to Scrum
“Definition of Done”
3) Make policies explicit
31. Certainty
Agreement
High
When to use Empirical?Kanban concepts
1) Visualize Value Stream
2) Limit Work In Process (WIP)
3) Make policies explicit
4) Manage Flow
Like Scrum
“Burndown
chart”
32. Certainty
Agreement
High
When to use Empirical?Kanban concepts
1) Visualize Value Stream
2) Limit Work In Process (WIP)
3) Make policies explicit
4) Manage Flow
5) Improve
Collaboratively
41. References:
Mini-book: Kanban & Scrum – Making the Best of Both (minibook)
http://www.infoq.com/minibooks/kanban-scrum-minibook
Scrum in 30 Seconds
https://www.scrumalliance.org/scrum/media/ScrumAllianceMedia/CSC%20CST
%20Resources/Scrum-in-30-seconds_poster.pdf
Book - Training Scrum (Growing Agile)
https://leanpub.com/TrainingScrum
Kanban Values, Principles, & Practices
http://agiletrail.com/2013/01/22/99-second-presentation-kanban-values-or-how-i-
almost-attacked-a-manager-with-hot-coffee/
Agile in the Large
http://scaledagileframework.com
http://disciplinedagiledelivery.com/lifecycle/
42. More References:
Scaled Agile Framework
http://scaledagileframework.com
Disciplined Agile Delivery
http://disciplinedagiledelivery.com/lifecycle/
Examining Different Approaches to Scaling Agile – Dolman & Spearman
http://www.infoq.com/news/2014/07/compare-agile-scaling
http://www.agilescaling.org/
43. Even More References:
What Allows Agile to Succeed in an Organization
http://www.leadingagile.com/2013/06/what-allows-agile-to-succeed-in-
an-organization/
Book – Agile Business: A Leader’s Guide to Harnessing Complexity
https://www.rallydev.com/agile-business-book
(disclaimer: Mark Kilby is one of the co-authors)
46. Certainty
Agreement
High
When to use Empirical?Kanban or Scrum?
Scrum Kanban
Project teams (5-9 people) Sustaining Teams
Planned work dominates Demand work dominates
High ability to estimate Low ability to estimate
Cross-functional capabilities Siloed capabilities
Self-contained Unbounded outside dependencies
Low variation in types of work High variation in types of work
Notas do Editor
I may not have time to do a Kanban exercise. So I’ll demonstrate throughout the session.
Anyone know this movie and the story between these characters?
This is from the Disney-Pixar Movie Cars (which my kids loved when it came out and I love it to). The red car is Lightning McQueen. A hot shot racer that no one can beat on the race track. The blue car on the left is Doc Hudson, the Lightning McQueen of his day 20+ years ago. Most of the first movie is about McQueen learning that he does not know everything and cannot use the same techniques in all situations. Doc proves this when he races McQueen on a dirt track and leaves him in the dust. Doc keeps repeating to McQueen that “Dirt is Different”.
But let’s not get off “track”. Let’s find out who is here with us and what you already know.
Please stand if you have read something about agile?
Keep standing if you have heard of the agile manifesto?
Keep standing if you have read the 4 values of the agile manifesto?
Keep standing if you have teams trying agile?
Keep standing if you have teams trying to live up to the agile manifesto?
Just to explain we’ll use these later and give them a chance to capture other questions.
15-20 min
Our defined approaches are like baking. When we know what we want, we can produce it efficiently. However, if there are changes, they become more costly and hard to change … especially in the Build phase. For instance, how likely are you to change the flavor by adding ingredients while something is already “in the oven”? Not likely.
20 years ago, many software engineers were wondering if there was a different approach. Could they work in short cycles? Could they use more of the “scientific method” to hypothesize what a customer needed, build the smallest possible slice, check it out with the customer and then, based on customer feedback, alter what they are building?
This is a bit like cooking. We add a pinch of this and taste. Based on what our senses tell us, we might add something different next.
Simple – requirements are well-understood and technology and approach are understood (WHAT AND HOW are clear)
Complicated – either requirements are not clear OR there is uncertainty with our approach (WHAT OR HOW are unclear
Complex – BOTH WHAT AND HOW are unclear
So our defined
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Key to empirical approaches is reducing waste. More when we talk about lean.
Just to explain we’ll use these later and give them a chance to capture other questions.
So remember, even when you think you know how to run that project, learn to inspect and adapt when you hit a road that’s different.
Key to empirical approaches is reducing waste. More when we talk about lean.