Catch the Wave: SAP Event-Driven and Data Streaming for the Intelligence Ente...
Kanban vs scrum
1. Kanban and Scrum are competitors or
friends?
Presented by: Maha Saad
1
2. Once upon a time
2
No process
Unrealistic process
No process
Both are unhappy They heard about scrum
Happily apply Scrum
Unrealistic process
Not always matchUnhappy again
4. • Software Processes
Is a division of software development work into distinct phases containing activities
with the intent of better planning and management.
• Why is Software Process nightmare?
• Inflexible, doesn’t fit organizational needs.
• Just a documentation nightmare.
• Adds overhead, extend project schedules.
• Needs over commitments
• Most of these legends based on bad process improvement experience.
Kanban and Scrum are competitors or friends? 4
Software process
legends.
SW process
Scrum
Kanban
Kanban vs Scrum
5. • For individuals:
• Reduces interruption and surprises “You work in your planned tasks”.
• Reduce reworks.
• For project:
• Improve ability to estimate tasks
• Reduce risk of surprises “requirements creep, nasty integration bugs”.
• Effective monitoring catches problems when they occur.
• For organization:
• Increase customer satisfaction as a result of improved product stability.
• Increase repeatability of success “facilitates more accurate strategic planning.
Kanban and Scrum are competitors or friends? 5
Why Software Process
is important?
SW process
Scrum
Kanban
Kanban vs Scrum
6. • Where are we now?
• When will it be done?
• Who is working on what?
• What should I be doing now?
Kanban and Scrum are competitors or friends? 6
Now at anytime you have
an answer for:
SW process
Scrum
Kanban
Kanban vs Scrum
7. Software Process models
SW process
Scrum
Kanban
Kanban vs Scrum
Agile
Kanban and Scrum are competitors or friends? 7
8. Kanban and Scrum are competitors or friends? 8
Is Agile a methodology?
SW process
Scrum
Kanban
Kanban vs Scrum
9. Kanban and Scrum are competitors or friends? 9
It’s an umbrella.
SW process
Scrum
Kanban
Kanban vs Scrum
10. • Principles:
• Split your organization into small, cross-functional, self-organizing teams.
• Split your work into a list of small deliverables.
• Sort the list by priority and estimate the relative effort
• Split time into short fixed-length iterations
• integrating regularly to see the whole.
• Activities:
Kanban and Scrum are competitors or friends? 10
Scrum principles and
activities.
SW process
Scrum
Kanban
Kanban vs Scrum
11. • It’s difficult to plan a project that lacks a clear definition.
• Scrum resists change within an iteration.
• Difficult to plan and commit for long iteration
• Difficult to fit stories in short iterations.
• It needs changing of my culture.
Kanban and Scrum are competitors or friends? 11
Scrum defects.
SW process
Scrum
Kanban
Kanban vs Scrum
12. • Kanban is Lean tool.
• Lean began in manufacturing environments (Toyota – Japan 1940).
• Production cycle cost quality
• Overproduction
• Holding inventory
• Waiting
• Non-Value-Added-Processing
• Defects
• Goals:
• Limit work in progress.
• Increase efficiency.
Kanban and Scrum are competitors or friends? 12
Kanban and Lean production
SW process
Scrum
Kanban
Kanban vs Scrum
13. • Solutions:
• Manufacture based upon a pull system
• Resources are provided on a just-in-time basis.
• Value Stream Mapping
• Focus only on few items
• Kanban (Visual signal/Card)
• A method for maintaining flow of material
• How much material is needed.
• From where the material is ordered.
• To where it should be delivered
• Other industries as SW start to follow Lean production
Kanban and Scrum are competitors or friends? 13
Kanban and Lean production
Cont…
SW process
Scrum
Kanban
Kanban vs Scrum
14. Kanban
• Principles:
• Visualize the workflow
• Limit WIP
• Measure the lead time
• Activities:
Map Your
Workflow
Visualize Work
in Process
Set Your Initial
WIP Limits
Get Kanban
Working
Look for
Bottlenecks
Inspect and
Adapt
Kanban and Scrum are competitors or friends? 14
Kanban principles and
activities.
SW process
Scrum
Kanban
Kanban vs Scrum
15. • Map the existing process not an ideal process.
• Start simple and add columns as necessary
• It will be enhanced iteratively.
Kanban and Scrum are competitors or friends? 15
Map Your Workflow
SW process
Scrum
Kanban
Kanban vs Scrum
16. Visualize your work
SW process
Scrum
Kanban
Kanban vs Scrum
Kanban and Scrum are competitors or friends? 16
17. • Take care
• Too low WIP limit => idle people => bad productivity
• Too high WIP limit => idle tasks => bad lead time
• You don’t have to get them exactly right the first time.
• Some recommendations:
• Setting low initial limits can be painful, but yields faster results.
• Setting high limits initially and lowering them over time may slower results.
• In progress stories = 0.5 * team members & story in queue = 0.5 in progress stories
• But you don’t want force developers to work together on stories
In progress stories = 1.5 * team members
Kanban and Scrum are competitors or friends? 17
Set your initial limit
SW process
Scrum
Kanban
Kanban vs Scrum
18. • Pull system
• One stage of the process pulls work from the previous stage.
• Giving the signal to the previous stage to make another one.
• This approach limits WIP
• Push system
• Each stage works as quickly as possible
• And then pushes work to the next
• No matter how much WIP already exists.
Kanban and Scrum are competitors or friends? 18
Get Kanban working
SW process
Scrum
Kanban
Kanban vs Scrum
19. • If your WIP limits are set well, you’ll hit a limit just as a bottleneck
begins to form.
Kanban and Scrum are competitors or friends? 19
Look for bottlenecks
SW process
Scrum
Kanban
Kanban vs Scrum
20. • Calculate your metrics as lead time, bottlenecks
• Update your parameters as WIP
• Start again.
Kanban and Scrum are competitors or friends? 20
Inspect and adapt
SW process
Scrum
Kanban
Kanban vs Scrum
21. Scrum Kanban
Time boxed iterations Fixed time iterations.
Sprint planning
then complete committed tasks.
then review & retrospective
Do scrum iteration
Or event driven iteration
Or do what fit with you
WIP Limits WIP per iteration Limits WIP per workflow state
Roles Prescribes 3 roles:
- Product Owner
- Team
- Scrum Master
Add the role you want BUT don’t
conflict with other elements of
the process
Feedback loops - Daily in standup.
- Every iteration in retrospective
- Select when you want to
analyze the metrics and make
changes
- Just like Scrum
Too long loop
improvement will be
slow.
Too short loop process
not have time to stabilize
between each change
Kanban and Scrum are competitors or friends? 21
Kanban Scrum comparison
(1/4)
SW process
Scrum
Kanban
Kanban vs Scrum
22. Scrum Kanban
Change requests Resists change within an iteration - Pull change as soon as there is a
capacity
- just like Scrum
Backlog items must fit in a sprint Yes No
Estimation <<Prescribed>>
Calculated via average velocity
and story points.
{V = nPoints/Iteration}
<<Not Prescribed>>
- break each item into roughly
equal pieces.
{V = nPecies/unit of time}
- Average lead time per MMF
- just like Scrum
- Use T-shirt sizes (S, M, L)
- Others…….
Kanban and Scrum are competitors or friends? 22
Kanban Scrum comparison
(2/4)
SW process
Scrum
Kanban
Kanban vs Scrum
23. Scrum Kanban
Product backlog prioritization Sorting the backlog by priority.
Changes to priorities take effect in
the next sprint.
Any prioritization scheme or none
- Always take the top item.
- Always take the oldest item
- Take any item
- Spend approximately 20% on
maintenance items and 80% on
new features.
- Split the team’s capacity
roughly evenly between
product A and product B ·
Empirical Yes Yes
23
Kanban Scrum comparison
(3/4)
SW process
Scrum
Kanban
Kanban vs Scrum
Kanban and Scrum are competitors or friends?
24. Scrum Kanban
Daily meetings <<Prescribed>>
people-oriented
<<Not prescribed BUT preferred>>
board-oriented
Support multiple
projects
Yes Yes
Charts Sprint and release
burndown charts
Any or none
Kanban and Scrum are competitors or friends? 24
Kanban Scrum comparison
(4/4)
SW process
Scrum
Kanban
Kanban vs Scrum
25. It’s not Agile
Kanban and Scrum are competitors or friends? 25
Is it Agile??????
SW process
Scrum
Kanban
Kanban vs Scrum
Iterations are
not prescribed
Roles are not
prescribed.
Charts are not
prescribed
AGAIN Agile
is values and
principles not
activities
26. You can have/do
vs
You should have/do
Kanban is not magic you should pay
Fewer constraints many parameters to think about
Kanban and Scrum are competitors or friends? 26
Kanban vs Scrum conclusion
SW process
Scrum
Kanban
Kanban vs Scrum
27. • Organizations are not ready for a radical overhaul
• You like scrum but not all activities and principles
Getting off the sofa and going for a marathon (Scrum) may cause a heart
attack
Kanban and Scrum are competitors or friends? 27
When can you use Kanban
SW process
Scrum
Kanban
Kanban vs Scrum
28. If process doesn’t match with you
Kanban and Scrum are competitors or friends? 28
Conclusion
Don’t doubt yourself and be Don’t doubt process concept and be Doubt process improvement and be
• Kanban and Scrum are friends
• It’s not everything about Kanban.
31. Thank you for your
attention
Kanban and Scrum are competitors or friends? 31
Editor's Notes
Proto type: start with prototype then involve customer and repeat till rich working software “It’s mix of more than one approaches”
Incremental development: mix waterfall and iterative -> it divide large sw into increments the apply the waterfall process for each increment
Agile vs Spiral -> Spiral is iterative agile is iterative and incremental , Spiral iteration is long and its output is prototype, agile iteration is short and its output is shippable product
Spiral is good for exploratory or uncertainty projects
Customer satisfaction by rapid delivery of useful software
Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months)
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Self-organizing teams
Regular adaptation to changing circumstances
Prinicibles:
- Split your organization into small, cross-functional, self-organizing teams.
Split your work into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item
Split time into short fixed-length iterations
Empirical Process Control
In Scrum, decisions are made based on observation and experimentation rather than on detailed upfront planning
Cross-functional teams collaborative
Scrum roles Self organized team
jumping from task to task, losing clarity on what to do next and what is most important, and increasing the complexity of the overall workload.
Pull system producing products just as customers order them
Toyota line-workers used a Kanban (i.e., an actual card) to signal steps in their manufacturing process.
Kanban is a tool for managing the flow of XXX in a process.” Xxx materials or information (or whatever)“
having too many parts on hand or too much work in process (WIP) is waste.
http://www.infoq.com/news/2009/05/kniberg-kanban-v-scrum
Visualize the workflowSplit the work into pieces, write each item on a card and put on the wall
Use named columns to illustrate where each item is in the workflow
Limit WIP (work in progress) – assign explicit limits to how many items may be in progress at each workflow state.
it reduces the time it takes to get any one thing done (lead time), and
it improves quality by giving greater focus to fewer tasks
Measure the lead time (average time to complete one item, sometimes called “cycle time”), optimize the process to make lead time as small and predictable as possible.
https://kanbanery.com/ebook/GettingStartedWithKanban.pdf
Map your work flow -> the real one not the one you dream “It will be improved later”
Every column divided to 2 sections in progress and buffer “Story move from in progress state to buffer state of next column
The numbers written on the bottom limit the number of stories allowed at each station (In progress + buffer).
When a column in a Kanban board is full, we know that group is at capacity. we learn pretty fast what’s slowing stories down from being completed and we can take steps to improve performance at the process point
Above the stories queue and each of the story process steps columns is an expedite slot, for urgent feature requests
The product owner can make changes to the Backlog and Selected columns any time “expedite and queue” he likes, but not the other columns.
- For each task track only what you need as Creation Date, Created by, Priority, Task Type and Description
For example testers pull implemented tasks to be tested only when they have no in progress tasks
Instead of developers push their to be tested tasks to them whatever they finished or not
http://www.crisp.se/file-uploads/Kanban-vs-Scrum.pdf
So let’s say we redreduce a WIP limit, based on the hypothesis that this will improve our process. We then observe how things like capacity, lead time, quality, and predictability change. We draw conclusions from the results and then change some more things, continuously improving our process.
. We draw conclusions from the results and then change some more things, continuously improving our process.
“Time box”
Every week we release whatever is ready for release. Every second week we have a planning meeting and update our priorities and release plans. Every fourth week we have a retrospective meeting to tweak and improve our process”
“Event drive”
We trigger a planning meeting whenever we start running out of stuff to do
We trigger a release whenever there is a MMF ready for release
We trigger a spontaneous quality circle whenever we bump into the same problem the second time
you are expected to experiment with the process and customize it to your environment
people-oriented ->every person reports one by one
Board oriented ->we might not necessarily have to hear everyone speak as long as we focus on the bottleneck parts of the board
Prescriptive means “more rules to follow” and adaptive means “fewer rules to follow”