SCRUMBAN?!?! What is it and how can it help your team?

SCRUMBAN?!?! What is it and how can it help your

team?

A Little About Me•Sr. Solutions Developer & BA with Leading EDJE in Columbus, Ohio

•Java Developer for 9 years in multiple industries•Passionate about Agile•Got my PMI-ACP in December of 2014•Currently prepping for the PSM I•Providing Agile coaching for my current Client

Itinerary• Agile Manifesto• Brief overview of Scrum• Brief overview of Kanban• Differences & Similarities• ScrumBan - examples and benefits• ScrumBan - Making it fit for your team• Questions

Agile Manifesto

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items onthe right, we value the items on the left more.

Scrum

Scrum FlowWhat does QA do at the beginning of the Sprint?

Do you notice that QA is causing a bottleneck?

Have you ‘failed’ a sprint due to QA testing not done?

How do you define a complete task? Is it written down?

Developer Pulls Story

Code StoryPass to QA

Story is Done

Project Backlog

Sprint Backlog

Kanban

Kanban Flow

Business Managers rarely understand the concept of “No End Date”

How do you determine when to do a Demo or Deployment?

Where is the reflection on process?

How is Change managed effectively and quickly?

Kanban Board w/Project Scope and WIP limits

Developer Reviews WIP

Developer pulls story or helps others

Pass to QAStory is Done

TODO In Progress Pending QA QA In Progress

Done

(3) (3) (2)

Example: Kanban Flow

Let’s CompareSimilarities:

• Prioritized backlog• Self-organizing teams• Follows the Agile Manifesto• QA part of the team

Major Differences:• Time Frame• Scheduled Demo’s• Scheduled Feedback• Retrospectives• Deployment Schedule

ScrumBan

ScrumBan Flow

Kanban Board w/Sprint Scope and WIP limits

Developer Reviews WIP

Developer pulls story or helps others

Pass to QAStory is Done

Project Backlog

Combine them:

Project Backlog from SCRUMSprint Backlog from SCRUMKanban board with WIP limits from KANBANHelping other groups from KANBANQA getting story ASAP from BOTH

Let’s CompareScrum Kanban ScrumBan

Scope Committed @ beginning of sprint

Priority driven Committed @ beginning of sprint

Timeframe Typically 2 weeks Open ended Typically 2 weeks

Flow Develop & Hand off to QA; No WIP limits

Fully cohesive team; Work together; Pair Programming; WIP Limits

QA starts scripts; Developers code & test when needed; Pair Programming; WIP Limits

Kanban Board for Typical Scrum Teams

TODO In Progress Pending QA QA In Progress

Done

QA BottleneckHigh In

Progress Amount

Streamlined ScrumBan Board

TODO In Progress Pending QA QA In Progress

Done

(4) (4) (3)

No BottleNeck

!

Work in Progress Limits

Benefits of ScrumBan

Best of Scrum & Kanban

WIP limits remove

bottlenecks

Retrospectives provide process improvements

Demo’s every Sprint

Timeframe for Business peace

of mind

QA involved from beginning

Fosters Cross-functional

Teams

How to Implement ScrumBan

• Implement Scrum Practices

• Create a Kanban Board

• Apply WIP Limits to each Swimlane

• Train team to be cross functional/ How to follow WIP limits

• Create a Definition of Done for each Swimlane

• Hold all Scrum meetings

Follow the Agile Manifesto

Minimum Take-aways

1. Self-organizing and cross-functional Teams - necessary

regardless of the methodology implemented.

2. Visual representation of process is VITAL to keep

everyone informed.

3. WIP limits & Definition of Done streamline the flow and

also allow for collaboration

Questions?

Thank You!Heather TooillLeading EDJE

Heather.Tooill@leadingedje.com@HeatherTooill

http://speakerrate.com/speakers/133371-htooill