Kanban game. Danske Bank version developed by Sune Lomholt based on Software development Kanban 2009-2010 Christina Skaskiw



Similar documents
The rest of this document describes how to facilitate a Danske Bank Kanban game.

Agile support with Kanban some tips and tricks By Tomas Björkholm

Software Development. Intermediate 2. Homework Booklet

Statistics New Zealand is Agile Continued Implementation of AGILE Process at Statistics NZ

Using a Lean and Kanban Approach in Agile Development. Jeff Patton AgileProductDesign.com jpatton@acm.org

Lean Software Development and Kanban

Agile Supercharged Scaling Agile as a Business Change Tool. James Yoxall Indigoblue Kevin Heery IPC Media Agile Business Conference

Math Board Games. For School or Home Education. by Teresa Evans. Copyright 2005 Teresa Evans. All rights reserved.

Program & Portfolio! Management using! Kanban! Copyright 2013 Davisbase Consulting. Limited Display License Provided to ASPE

ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )

Lean Metrics How to measure and improve the flow of work. Chris Hefley, CEO of LeanKit. November 5 th, 2014

Agile and lean methods for managing application development process

Software Engineering Process Economy & Quality

Scrum vs. Kanban vs. Scrumban

AGILE BUSINESS INTELLIGENCE

Value, Flow, Quality BCS PRACTITIONER CERTIFICATE IN AGILE SYLLABUS

Utilisation v Productivity who gets the gold medal? Margaret Morgan Helen Meek

Lean Healthcare Metrics Guide

We are a DIGITAL EXPERIENCE AGENCY

Three daily lessons. Year 5

Agile Training Portfolio

agenda AGILE AT SCALE

The metrics that matter

MATHEMATICS Y3 Using and applying mathematics 3810 Solve mathematical puzzles and investigate. Equipment MathSphere

XP 2015 Presenter-Nirnaya Tripathi Date

Focused Objective 6/20/2011

Game 9. Overview. Materials. Recommended Grades 3 5 Time Instruction: minutes Independent Play: minutes

Getting Started with Kanban Paul Klipp

Information Sharing Lessons Learned from Gateway Reviews: Gate 5 Benefits Realisation Review

SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization

Managing Your Way to Success ensuring economic, effective, efficient quality best practice service (every time)

Cloud Infrastructure Security Management

Measuring Program Effectiveness an introduction to the Performance Dashboard. Objectives

Five daily lessons. Pages 24, 28. Page 32. Page 60. Year 2

WHY KANBAN? Troy Tuttle. blog.troytuttle.com. twitter.com/troytuttle. linkedin.com/in/troytuttle. Project Lead Consultant, AdventureTech

How to measure productivity in software development

Scaling Agile with the Lessons of Lean Product Development Flow Copyright 2012 Net Objectives, Inc. All Rights Reserved

Measuring ROI of Agile Transformation

Secrets of a Scrum Master: Agile Practices for the Service Desk

WE ARE FOCUSED ON HELPING OUR CLIENTS WORK SMARTER AND MORE EFFICIENTLY SO THAT TOGETHER, WE CAN EMPOWER PEOPLE TO DELIVER GREAT RESULTS.

HP DevOps by Design. Your Readiness for Continuous Innovation Rony Van Hove/ April 2 nd, HP Software: Apps meet Ops 2015

Designing your Kanban Board to Map your Process

Agile and lean methods for managing application development process

Assignment 1: Your Best Backlog

Kanban. Marek Majchrzak, Andrzej Bednarz Wrocław,

Management. Customer Relationship Management /1. Establishing CRM successfully. The essence of Customer relationship Management

Kanban for large scale off-shored mobile.de. January Munich. Feedback to mandrezak@team.mobile.de

POSITION DESCRIPTION ORCID Technical Support Analyst/Coordinator

Overview SFLOLC1. Develop and implement a management system to ensure

Two years of applying Kanban at SAP: a report from the trenches

Change & configuration management

Digital Marketing Specialist

A Kanban System for Software Engineering

Evolving Agile Testing

Release Notes Applied SAFe 4.0

BALANCED SCORECARD What is the Balanced Scorecard?

10 kanban boards and their context

Tool 3 What makes a job satisfying for you?

J-Curve effect, 38, JIT. See Just-in-Time Inventory Just Enough Design Initially (JEDI), 6, 283

ERP project manager. Plan and manage your ERP project in a way that creates business impact, while making user experience a safe transition.

From PvE & Priorities to a plan. Part 2: MVP & planning

How To Plan An Agile Project

Lean and Kanban at Scale Extending Kanban across the portfolio, program and team levels. Al Shalloway, Net Objectives. September 4 th, 2014

NOS for Data Analysis (802) September 2014 V1.3

Enabling the Digital Enterprise

Agile in a Safety Critical world

The Flu Pandemic Game A business continuity training resource for GP practices.

PHSO. Employee Survey Feedback & Planning

How to Grow and Sell a Franchise Business

What is meant by the term, Lean Software Development? November 2014

Unit 10: Software Quality

Digital Marketing Specialist

Lead Generation & Nurturing Benchmarking Report

Agile Certification: PMI-ACP

PROJECT PORTFOLIO MANAGEMENT: THE ISSUES, CHALLENGES, BUSINESS OPPORTUNITIES AND FUTURE TRENDS

Agile Metrics - What You Need to, Want to, and Can Measure. June 9, 2014

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Service Road Map for ANDS Core Infrastructure and Applications Programs

Kanban. A Toyota s manufacturing system for Software Development CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH. Eloy Reguero Fuentes

Overview of Future Purchasing s fundamental and advanced training workshops...

MasterClass 26 th March 2015 DevOps and Continuous Deployment

Get Dirty with Diagnostics: Agile Performance Tuning at the Lowest Level

Business Solutions Manager Self and contribution to Team. Information Services

Thursday, October 18, 2001 Page: 1 STAT 305. Solutions

Jane Deal Chief Information Officer, Citizens Advice (Former Head of IKS at RNIB)

PROTEUS Enterprise - IT Governance, Risk and Compliance Management Solution

Writing Samples Using the 5 Point/Level Employee Performance Rating Scale

Use Blackboard 9.1 Auto-Submit and Provide a more time accommodation

The capstone course as a means for teaching agile software development through project-based learning

Measuring the effectiveness of testing using DDP

VISUAL REQUIREMENTS MANAGEMENT WITH KANBAN. Mahesh Singh Co-founder/ Sr. VP Product, Digite, Inc.

Teaching an Elephant to Dance. Patterns and Practices for Scaling Agility

Baseball Multiplication Objective To practice multiplication facts.

ARCHER SP Service Quarterly Report. Quarter

Modeling, Simulation & Data Mining: Answering Tough Cost, Date & Staff Forecasts Questions

Customer Experience Benchmarking

Case Study: ICICI BANK INTERNAL AUDIT DEPARTMENT PENTANA AUDIT WORK SYSTEM IMPLEMENTATION

Sustaining sports development: A new phase

Providing standards, methodologies and a set of PM tools. Promoting project management within the organisation

LESSON 7 Don t Be A Square by Michael Torres

Transcription:

Kanban game Danske Bank version developed by Sune Lomholt based on Software development Kanban

Kanban Game Backlog Planned Analysis Development Test Deploy Done Doing Done Doing Done Doing Done

Redistribute dice every round Dice score not used are lost Change WIP limit if needed Dice rules: Dice moved to other column counts half Roll 1 & 2 = a roll of 1 Roll 3 & 4 = a roll of 2 Roll 5 & 6 = a roll of 3 Rules Regular story: Cycle time 4 rounds = 100% business value 5 rounds = 75 % business value 6 rounds = 50 % business value 7 rounds = 25 % business value > 7 rounds = 0 business value Cycle time = Complete - Started Fixed date story: Must complete on deadline Only value when on time Lead and cycle time irrelevant for gaining business value Expedite story: Must complete in 3 rounds (cycle time = 3) Can break WIP limits Only value when on time Must be done even if no value

Round 0 1) Spend 5 minutes to organise the normal (white) stories and fixed date (yellow) stories in the backlog 2) Now select 5 stories to start with and place these in prioritised order in the planned column 3) In each of these stories write 0 in the field Planned in round

Round 1 1) Plan work 1) Select which stories from the Planned column you want work on into Analysis - doing 2) Ensure the stories are in prioritised order 3) Write when work began in the field Started in round write 1 4) Decide if you want to move stories from the Backlog into the Planned column. If so remember to fill out the field Planned in round with 1 5) Decide how many dice you want to utilise in analysis (hint: remember you can move dices around, but only use them once in each round) 2) Do work 1) Roll the dice 2) Assign dice to stories in prioritised order, if enough dice just cross out the field Analyse. If not enough write how many dice is left on the card. 3) Move stories that are done from the doing to the done column. 3) Update metrics

Round 2 It is important that you work you way through the board from right to left 1) Plan work 1) Select which stories in the Analysis Done column you want to work on in Development. Move these from Analysis Done to Development Doing. 2) Consider if you want to move any stories from Planned to Analysis Doing (remember to fill in the field started in round ) 3) Decide if you want to move stories from the Backlog into the Planned column. If so remember to fill out the field Planned in round with 2 4) Ensure the stories are in prioritised order in all columns 5) Decide how many dice you want to utilise in analysis and development (hint: remember you can move dices around, but only use them once in each round) 2) Do work 1) Roll the dice for development 2) Assign dice to stories in prioritised order, if enough dice just cross out the field Develop. If not enough write how many dice is left on the card. 3) Move stories that are done from the doing to the done column. 4) Roll the dice for Analyse 5) Assign dice to stories in prioritised order, if enough dice just cross out the field Analyse. If not enough write how many dice is left on the card. 6) Move stories that are done from the doing to the done column. 3) Update metrics

Round 3 It is important that you work you way through the board from right to left 1) Plan work 1) Select which stories in the Development Done column you want to work on in Test. Move these from Development Done to Test Doing. 2) Select which stories in the Analysis Done column you want to work on in Development. Move these from Analysis Done to Development Doing. 3) Consider if you want to move any stories from Planned to Analysis Doing (remember to fill in the field started in round ) 4) Decide if you want to move stories from the Backlog into the Planned column. If so remember to fill out the field Planned in round with 3 5) Ensure the stories are in prioritised order in all columns 6) Decide how many dice you want to utilise in analysis, development and test (hint: remember you can move dices around, but only use them once in each round) 2) Do work 1) Roll the dice for test 2) Assign dice to stories in prioritised order, if enough dice just cross out the field Test. If not enough write how many dice is left on the card. 3) Move stories that are done from the doing to the done column. 4) Roll the dice for development 5) Assign dice to stories in prioritised order, if enough dice just cross out the field Develop. If not enough write how many dice is left on the card. 6) Move stories that are done from the doing to the done column. 7) Roll the dice for analysis 8) Assign dice to stories in prioritised order, if enough dice just cross out the field Analyse. If not enough write how many dice is left on the card. 9) Move stories that are done from the doing to the done column. 3) Update metrics

Round n > 3 It is important that you work you way through the board from right to left 1) Plan work 1) Select which stories in the Test Done column you want to work on in Deploy. Move these from Test Done to Deploy. 2) Select which stories in the Development Done column you want to work on in Test. Move these from Development Done to Test Doing. 3) Select which stories in the Analysis Done column you want to work on in Development. Move these from Analysis Done to Development Doing. 4) Consider if you want to move any stories from Planned to Analysis Doing (remember to fill in the field started in round ) 5) Decide if you want to move stories from the Backlog into the Planned column. If so remember to fill out the field Planned in round with 3 6) Ensure the stories are in prioritised order in all columns 7) Decide how many dice you want to utilise in analysis, development, test and deploy (hint: remember you can move dices around, but only use them once in each round) 2) Do work 1) Rolls the dice for deploy 2) Assign dice to stories in prioritised order, if enough dice just cross out the field Deploy. If not enough write how many dice is left on the card. 3) Move stories that are done from the deploy to the Done column. 4) Roll the dice for test 5) Assign dice to stories in prioritised order, if enough dice just cross out the field Test. If not enough write how many dice is left on the card. 6) Move stories that are done from the doing to the done column. 7) Roll the dice for development 8) Assign dice to stories in prioritised order, if enough dice just cross out the field Develop. If not enough write how many dice is left on the card. 9) Move stories that are done from the doing to the done column. 10) Roll the dice for Analysis 11) Assign dice to stories in prioritised order, if enough dice just cross out the field Analyse. If not enough write how many dice is left on the card. 12) Move stories that are done from the doing to the done column. 3) Update metrics

Kanban Game reflection questions Did you see the six core practices in the game? Visualise work Limit Work In Progress (WIP) Make policies explicit Measure and Manage Flow Implement feedback loops Improve collaboratively using scientific models

Kanban Game reflection questions Did you see the six core practices in the game? What do the measurements show you? How did the expedite and fixed date (round) impact the flow? What happened before each round? What about lost Business Value? Why have a planned column? What was the impact of introducing the WIP limit?