Как совместить scrum и kanban

www.ciklum.net

How to Mix Scrum and Kanban

Vladimir Gorshunov

Ciklum Services & Consulting (CSC)

Consultant profile

www.ciklum.net 2

Vladimir has more then 9 years in software development and for 4 years he is building efficient distributed agile teams, which are able to deliver business value on-time and on-target using best industry practices.

Vladimir expert with Java technical background and has been involved in different projects from the variety of business domains (Banking Solutions, Mobile Development, High Loading Computation, Payment Systems, Customer Experience Management, Government Systems, etc.)

Vladimir Gorshunov• Ciklum Technical Consultant / Program

Manager• Agile Coach, Certified Scrum Product

Owner, Certified Scrum Master• Experienced Agile Project Manager with

technical background

Three stories…

www.ciklum.net 3

First story…

www.ciklum.net 4

What is mobile development forYOU?

www.ciklum.net 5

What is mobile development?

Less that 3-4 people in the team Too much overhead with all the meetings -

actually wastes of time

Very short projects Not enough time to adapt if the initial plans

aren’t very accurate

www.ciklum.net 6

What is mobile development?

Can’t keep fully dedicated QA for one project QA is a shared resource, sometimes even remote

resource

Even developers are shared between projects!

Just do it! ASAP! Client doesn’t care about your internal process, he

needs a product

www.ciklum.net 7

Scrum practices (9) Scrum Master Product Owner Team Sprint planning meeting Daily Scrum Sprint review Product backlog Sprint backlog Burndown chart

www.ciklum.net 8

Scrum doesn't fit all

www.ciklum.net 9

Kanban practices (3)

Visualize the work flow (Board) Limit WIP (work in progress) Measure and optimize lead time (cycle time)

www.ciklum.net 10

Kanban doesn't fit all

www.ciklum.net 11

Scrum vs Kanban?

www.ciklum.net 12

We can use them together!

Scrum + Kanban in mobile dev

Less that 3-4 people in the team. Too much overhead with all the meetings -

actually wastes of time.

Keep daily meeting, planning and demo, process improvement can be done during all process or you can have retrospective at the end of every two sprints.

www.ciklum.net 13

Scrum + Kanban in mobile dev

Very short projects Not enough time to adapt if the initial plans

aren’t very accurate

You can use one week sprint instead of long 2-3 week sprint. You can even make demo or provide demo build two times per week.

You develop many projects, so you can adopt you process across all of your projects.

www.ciklum.net 14

Scrum + Kanban in mobile dev

Can’t keep fully dedicated QA for one project QA is a shared resource, sometimes it is even

a remote resource.

Include QA in common process, and in visualize testing activities too.

www.ciklum.net 15

Scrum + Kanban in mobile dev

Even developers are shared between projects

Limit WIP Adopt your process in all your projects Visualize the workflow

www.ciklum.net 16

Scrum + Kanban in mobile dev

Just do it! ASAP! Client doesn’t care about your internal

process, he needs a product.

That is TRUE!!! Be proactive, explain AGILE way of doing

things.

www.ciklum.net 17

Second story…

www.ciklum.net 18

What is NEW product development for YOU?

www.ciklum.net 19

What is new product development?

There are a lot of ideas from business.

It is hard to determine how many developers we ready need.

Let’s use what we used before!

www.ciklum.net 20

What is new product development?

Let’s start from a “green field”!

We need QA only at the end of the project!

Development team use agile, but designers don’t use it.

www.ciklum.net 21

What is new product development?

There are a lot of ideas from business. That is great, isn’t it? Put all ideas in your

backlog, coach or hire Product Owner. Does your customer have a CTO?

It is hard to determine how many developers we ready need. Scale your team as soon as you will have

enough job them.

www.ciklum.net 22

Agile and new product development

Let’s use what we used before!

Review all your decisions on retrospectives, sometimes it can be easier to use new solution instead of adopting an old one.

Let’s start from a “green field”!

Please, be pragmatic, use existing solutions and practices.

www.ciklum.net 23

Agile and new product development

We need QA only at the end of the project!

QA in agile team needs to test user stories before they will come to team, good QA will be a Product Owner assistance.

Developers use agile, designers don’t.

Integrate designers in you agile process, stop thinking about design as a solid thing.

www.ciklum.net 24

Third story…

www.ciklum.net 25

What is online service for YOU?

www.ciklum.net 26

What is online service?

Urgent tasks that need to be done NOW.

Business has interest in the time-to-market.

www.ciklum.net 27

Scrumban – mix Scrum and Kanban

www.ciklum.net 28

Scrumban iterations

Scrum-like planning & iterations.

Measure average things released per iteration.

Use Cumulative Flow diagram instead of Burndown.

www.ciklum.net 29

Scrumban flow

“Ready to development” column simplify what can be done next.

Use the late pulling tasks by developers.

Not everyone needs to have at least one task in progress.

www.ciklum.net 30

The Final step is Pull (or prioritization-on-demand)

www.ciklum.net 31

One size doesn't fit all

Questions?

www.ciklum.net 32

Vladimir Gorshunov

Ciklum Technical Consultant/Program Manager

vlg@ciklum.com

+375 29 601 33 44

skype: vladimir.gorshunov