[AV] Monthly Event - Jun 2015 - Scrumban for small production team working on multiple projects
Post on 12-Aug-2015
118 Views
Preview:
Transcript
I’m Khanh
2
Agile Enthusiast - Board Member of Agile Vietnam
Co-founder and PM at Silver Lining Ltd. - Mobile Development Agency.
Currently Project Manager of Studio 60
In this short talk we’ll cover:Common challenges in adopting agile (especially Scrum) in a small team working in multiple projects.
What is a Kanban System and how does it apply to software development?
Why Scrumban is the right fit for us ?
How do we work?
How do we plan?
How do we measure?
3
Our case
One team - Multiple Projects
Change popups everyday
Each member work for multiple projects at the same time
Tend to be specialized in single field
4
Time-boxed has common challenges when work on multiple projects.
Quality of requirements suffers
PO rush to prepare for upcoming cycles.
Quality of current development suffers
as client is unable to inspect software and answer question.
Quality often suffers
testers race to complete work late in the development time-box
Unpredictable work makes it difficult to plan even a few weeks in advance
5
Inside an iteration, effort across roles is unevenTesting starts late and never seems to get enough time
6
– Sebastian Sussmann - CIO, Axon Active Viet Nam
“Produce hidden problems, “undone work” and bad code.”
7
What happen when we push the team?
Then
Instead of focusing on circle with an iterative model we should focus on smoothing flow which allows us to work on multiple projects but still get enough efficiency.
9
Kanban principles
A pull method
Visualize workflow
Limit Work-In-Progress
Pull Work, not Push
Monitor & Refine
11
Current implement - Scrum practicePros:
Iterative and incremental method
Adaptability for product development
Regular feedback bw team and Product Owner
Regular communication amongst team
13
Cons:
• Requires experienced team
• Time expenses for planning, review.
• Slow response cycle
• Overfill/under-fill a sprint backlog
Kanban
14
Pros:
• Reduces waste and scrap
• Responsive to changes
• Increases productivity and efficiency
• Focus on the most important
Cons:
• Forward planning really difficult
• Bottlenecks
Scrumban
15
• Saving time: planning on demand technique
• Responsive to changes
• Waste minimization: transparent workflow to show weaknesses and opportunities to improve the process
How do we plan?Iteration planning every week
Update charts and board. (Done projects where moved to a “Bottle of Done”.)
Look back at the last week. What happened? Why?
What could be done to improve it?
Readjustment of WIP limit (if needed).
Task breakdown and estimation of new project [if needed].
32
Referenceshttp://www.352inc.com/blog/scrum-vs-kanban-choosing-an-agile-method-for-your-product/
http://www.attendly.com/how-digital-agencies-around-the-world-manage-their-projects/
https://davidmarquis.wordpress.com/2011/12/03/83745499/
https://www.youtube.com/watch?v=502ILHjX9EE
Kanban and Scrum making the most of both - Henrik Kniberg & Mattias Skarin
43
Thank you!
Contact me at:
khanh@agilevietnam.org
Twitter: @mynamelskhanh
http://phanduykhanh.com
44
top related