[AV] Monthly Event - Jun 2015 - Scrumban for small production team working on multiple projects

Scrumban for small team working on multiple projectsBy Khanh Phan

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?

Watch a clip

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

8

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

10

Kanban principles

A pull method

Visualize workflow

Limit Work-In-Progress

Pull Work, not Push

Monitor & Refine

11

Kanban boards visualize flow

12

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 work?

16

How do we work?Iteration planning every week

17

How do we work?Create and visualize workflow

18

How do we work?Daily standup

19

One day in Scrumban land

20

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

21

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

22

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

23

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

24

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

25

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

26

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

27

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

28

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

29

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

30

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

One day in Scrumban land

31

Kanban and Scrum making the most of both Henrik Kniberg & Mattias Skarin

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

How do we plan?

33

Previously

How do we plan?

34

Now

How do we plan?

35

Now

How do we plan?

36

Now

How do we measure?

37

How do we measure?

38

Measure:

• Velocity per work type

And result

39

And result

40

Team

41

Q&A

42

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:

[email protected]

Twitter: @mynamelskhanh

http://phanduykhanh.com

44