Why we transitioned from Scrum to ScrumBan

DYANESHWARAN PERIYASAMYSENIOR CONSULTANT

THE OPINIONS EXPRESSED HERE REPRESENT MY OWN AND NOT THOSE OF MY EMPLOYER.

Who am I?

Agile Coaching / Consulting / Training

Enterprise Agile Transformation Scaled Agile Framework (SAFe), DevOps

Agile Software Development Methodologies Scrum – Six years as Scrum Master and Iteration Manager

XP – Continuous Integration, ATDD, TDD and Pair Programming

Lean Thinking Applying Kanban

Lean management

Agenda

1. Starting pointi. Problems faced

2. Why ScrumBan?3. What is ScrumBan?4. After the transition!5. How we did it?

i. Metricsii. Tool configuration

6. Benefits and Challenges7. Q&A

Starting Point

•Product backlog creation (requirements workshop with Business and IT stakeholders)

•Release Planning, Iteration 0•Scrum ceremonies•Continuous Integration•One click deployment to UAT•Behavior Driven Development (BDD)

Scrum + XP

•Two scrum teams•Eight members in each team•Team members are located across three different cities•5 ½ hour time difference between Bangalore and remote teams•Specialized skill set (i.e.) not a cross functional team!•Scrum Master, Business Analysts, Tech Lead, Architect, Program Manager

Distributed Teams

Problems faced

Backlog

BA – Defines Business Rules

Developer –Implements the functionality

HTML Developer – Prepares GUI

prototypes

Tester –Validates the implementation

Product Owner – Accepts the user story

Who will provide inputs and

approve my prototype?

Too much work load on me. Need

more BAs!

No acceptance criteria!

Is there any work for me?

Come on guys, show me a completed

story.

Why ScrumBan? 1/3

Specialized Skill Set• BA, Architect, GUI

Designer, Developer, Tester, etc.

• Handover of work in the process of getting it DONE.

Distributed Teams• Multiple time zones• Limit ‘Work In Progress’

(WIP)• Focus on cycle time

Time Boxed Development• Iteration planning• Focus on iteration

goals• Value based Agile

SoW with the client

Why ScrumBan? 2/3

Bangaloreteam

RemoteTeam 1

Remote Team 2

Scrum ScrumBan

Why ScrumBan? 3/3

Required for release planning Time to market How much value can we deliver by Mar 2014?

Agile SoW Billing of contractors SoW extension based on number of iterations required Stop the project when enough value is generated

Iteration Goals Focus on planned user stories

What is ScrumBan?

Scrum(Time boxing)

Kanban(Work flow) ScrumBan

After transition!

BA – Defines Business Rules

New Ready for Dev

In Analysis

Developer –Implements the functionality

In Dev

Ready for

Testing

In TestingDone

HTML Developer –Prepares GUI prototypes

Tester – Validates the implementation

Product Owner – Accepts the user story

Showcase

How we did it? 1/3

How we did it? 2/3

How we did it? 3/3

How we did it?

Simple – just define the values for the property ‘Story Status’!

Scrum ScrumBan: Our benefits

Team’s morale has gone up Team members started enjoying their work Improvement in team’s velocity BAs are happy to write business rules for future user

stories Confident commitment Continuous improvement mindset QA specialist became part of the scrum team Collaboration between development and testing

Scrum ScrumBan: Our challenges

Measuring ‘Velocity’ is complicated since the user stories are NOT moved to DONE in one iteration

Complicated release planning due to Kanban flow User stories needs to be moved from one iteration to

another. But tasks are accomplished across multiple iterations. Tool support is required.

Capturing individual’s effort in the tool for the purpose of billing in client vendor model

Reachable @

Twitter: @dyaneshwaran_p

LinkedIn: https://in.linkedin.com/in/dyaneshwaran