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 tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

Scrum

Scrum Flow What 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? Project Backlog Sprint Backlog Developer Pulls Story Code Story Pass to QA Story is Done

Kanban

Kanban Flow Kanban Board w/Project Scope and WIP limits Developer Reviews WIP Developer pulls story or helps others Pass to QA Story is Done 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?

Example: Kanban Flow TODO In Progress Pending QA QA In Progress Done (3) (2)

Let’s Compare Similarities: 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 Combine them: Project Backlog from SCRUM Sprint Backlog from SCRUM Kanban board with WIP limits from KANBAN Helping other groups from KANBAN QA getting story ASAP from BOTH Kanban Board w/Sprint Scope and WIP limits Developer Reviews WIP Developer pulls story or helps others Pass to QA Story is Done

Let’s Compare Scrum Kanban ScrumBan Scope Timeframe Flow Committed @ beginning of sprint Priority driven Timeframe Typically 2 weeks Open ended 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 Bottleneck High In Progress Amount

Streamlined ScrumBan Board TODO In Progress Pending QA QA In Progress Done (4) (3) Work in Progress Limits No BottleNeck!

Benefits of ScrumBan Fosters Cross-functional Teams Retrospectives provide process improvements Best of Scrum & Kanban Timeframe for Business peace of mind Demo’s every Sprint WIP limits remove bottlenecks QA involved from beginning

How to Implement ScrumBan Implement Scrum Practices Create a Kanban Board Apply WIP Limits to each Swimlane Create a Definition of Done for each Swimlane Train team to be cross functional/ How to follow WIP limits Hold all Scrum meetings Follow the Agile Manifesto

Minimum Take-aways Self-organizing and cross-functional Teams - necessary regardless of the methodology implemented. Visual representation of process is VITAL to keep everyone informed. WIP limits & Definition of Done streamline the flow and also allow for collaboration

Questions?

Thank You! Heather Tooill Leading EDJE Heather.Tooill@leadingedje.com http://speakerrate.com/speakers/133371-htooill