Sharing talk: Scrumban for small production team working on multiple projects Scroll down for English: Tình huống: Bạn có nhóm phát triển nhỏ gồm 5-6 người cùng với nhiều dự án cỡ nhỏ (từ 2-4 tuần, nhiều khi nhiều hơn hoặc ít hơn). Đây là tình huống thường gặp ở những production house của các agency, những team nhỏ chạy những dịch vụ cho client hoặc team của một product trong đó có nhiều mảng cần chia ra: client Web, client iOS App, client Android App, Campaign microsite... • Một team - Nhiều dự án cùng lúc • Ưu tiên có thể thay đổi từng ngày • Mỗi thành viên đóng góp cho nhiều dự án khác nhau • Một thành viên có một chuyên môn riêng. Back-end dev, front end-dev, designer.. Vậy cách bạn chạy như thế nào để phù hợp với tình huống của team? Scrum liệu có phù hợp ? Hay là Kanban? Hay là còn cách nào khác nữa? Xin hãy sắp xếp thời gian của bạn có đủ 2 tiếng thư thả tham gia Agile monthly event Hồ Chí Minh tháng 6 này lúc 18h30 đến 20h30 tối thứ năm ngày 18/06/2015. Context: You have a small team of 5-6 people, evolving in a highly dynamic environment with small projects (2-4 weeks, sometimes less, sometimes more). This is a very usual situation in production house of agencies, or smaller teams dedicated to professional services (services to clients), or a product with many components which need to maintain and support: client Web, client iOS App, client Android App, campaign microsite... • One team - Multiple Projects • Changes popups everyday • Each member is spread between multiple projects at the same time • Tend to be specified in a single field How does Agile help you run the team in that kind of context? Scrum? Or Kanban? Or anything else? Please come and share with us your valuable experience while doing Agile software development next Thursday at our monthly event: 18.30 - 20.30 June 18th, 2015

1. Scrumban for small team
working on multiple projects
By Khanh Phan

2. 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

3. 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

4. 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

5. 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

6. Inside an iteration, effort across roles is
uneven
Testing starts late and never seems to get enough time
6

7. – Sebastian Sussmann - CIO, Axon Active Viet Nam
“Produce hidden problems, “undone work” and bad
code.”
7
What happen when we push
the team?

8. Watch a clip
https://www.youtube.com/watch?v=8NPzLBSBzPI
8

9. 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

10. Kanban
10

11. Kanban principles
A pull method
Visualize workflow
Limit Work-In-Progress
Pull Work, not Push
Monitor & Refine
11

12. Kanban boards
visualize flow
12

13. Current implement - Scrum
practice
Pros:
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

14. 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

15. Scrumban
15
• Saving time: planning on demand technique
• Responsive to changes
• Waste minimization: transparent workflow to show
weaknesses and opportunities to improve the process

16. How do we work?
16

17. How do we work?
Iteration planning every week
17

18. How do we work?
Create and visualize workflow
18

19. How do we work?
Daily standup
19

20. One day in Scrumban land
20
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

21. One day in Scrumban land
21
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

22. One day in Scrumban land
22
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

23. One day in Scrumban land
23
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

24. One day in Scrumban land
24
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

25. One day in Scrumban land
25
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

26. One day in Scrumban land
26
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

27. One day in Scrumban land
27
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

28. One day in Scrumban land
28
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

29. One day in Scrumban land
29
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

30. One day in Scrumban land
30
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

31. One day in Scrumban land
31
Kanban and Scrum making the most of both
Henrik Kniberg & Mattias Skarin

32. 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

33. How do we plan?
33
Previously

34. How do we plan?
34
Now

35. How do we plan?
35
Now

36. How do we plan?
36
Now

37. How do we measure?
37

38. How do we measure?
38
Measure:
• Velocity per work type

39. And result
39

40. And result
40

41. Team
41

42. Q&A
42

43. References
http://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

44. Thank you!
Contact me at:
khanh@agilevietnam.org
Twitter: @mynamelskhanh
http://phanduykhanh.com
44