10 kanban boards and their context

Transcription

1 10 kanban boards and their context Hi! I ve visualized a set of kanban boards from operations, development and sales to trigger ideas. But don t forget, a kanban board is a tool to help you think for yourself, in your context. So remember to apply the work in progress limits, policies and cadencies that is right for you. Never copy, only improve - Mattias Skarin Dude, what s kanban? 1

2 Scrum team applying WIP limits Work in progress limit Scrum team T I W D orem ipsum dolor sit amet, co nse ctetur Sun [3] orem ipsum dolor sit amet, co nse ctetur Why? To trigger a shift from a burndown like this.. orem ipsum dolor sit amet, co nse ctetur Rob Jane To something more like: 2

3 Development team using defined process WIP limit Ready buffer Development team combined with specialists New Test design In Dev User Test Deploy [1] [3] [3] [5] In progr. In progr. In progr. Queue In progr - Product owner / Project manager Polices are clear WIP in each step Ready buffer s from which next step can pull work Risks identified 1 Happy path test case Has a testcase Tag! In CI In stage Buildfile updated User happy! New column can get messy if no person maintains it Visible policies A buffer is a trade-off between cycle time and variance absorbtion 3

4 Development team with multiple clients Prod issue New Estimate New In Work Custom solutions dev team with project manager - Customer A - Customer B - Other teams - Platform architects In progr. Active projects Test design [2] Code Test Package [3] [3] [6] Projects and features visible WIP in each step Estimations can be regular /or on need triggered event Tempting to default features to time constrained (even though there really isn t any costly delay consequence) Classes of services in use: Time constrained feature Ordinary feature Bug Fixing tech debt To risk balance your portfolio, limit the amount of each category allowed on the board at any time 4

5 Development team with completion prediction Development team New Selected In Work Dev complete Selected Dev ready Feature - Product owner / Project manager Tasks Mon Tue Wed Thu Fri Completion date visible Learning of prediction towards cycle Chris Matts If estimated size > 5d task is broken down further When developer starts a task it is placed on the day they think it will finish. Each day, this prediction is updated. 5

6 Multi tier kanban with swimlanes Requests in progress [9] Features in progress [5] Dev in progress [3] x Development teams Analysts, Testers New requests Decompose Active Analyze Dev Verify Acc test - Business units - CTO - Architects Add limits all stages of the design cycle Synchronises flow of cooperative work by specialists and generalists You may need a big enough area in front of the board to gather around 6

7 System administration Prio Flow Prod Release Dev Support Project A Project B System administrator team supporting development and production - Production site - Development teams - Internal projects - Testers Course grained prio visible WIP balanced across work types Visible learnings opportunities for team members in maintainance and project work In work [8] Break down New Newly arrived reguests can get messy if no person maintains it 7

8 Operations - business process maintenance Production problem Flow New Find cause Fix cause! Course grained Prio - Production site - Business functions - Business planning dept. - Development team Planned business need (High impact) (Low impact) Due 2 months Due 1 month Due 1 week In work [3] Time and scope visibility WIP limits can be difficult to review Routine Unplanned Platform improvements New New Committed [1] Committed [1] In work [2] In work [1] Test [2] Test [2] 8

9 First line support Flow Questions Prio Need feedback from client! - Customer developers - Customer users - Sales - Architects Customer bugs Own platform bugs On hold get contract! Improvements Need help from specialist Solving Awaiting confirmation Call up client Time and scope visibility WIP limits can be difficult to review Signal to get or confirm client support contract (sales) Signal to pull specialist skill in (architects) Signal to call client up for confirmation (manager) 9

10 Second line support No of new incidents not addressed (yesterday) Address root cause, (one at a time) Backlog New Investigate [3] Follow up [6] Painkiller [1] Overflow { 0 } - First line support - Development teams - Operations managers High prio The rest In work [1] Backlog Wip limits on follow up work Focus on one root cause at a time, stay with it until fixed Not all incidents can go on the board - requires size limitation or similar for tasks on the board to avoid overadministration Wip Overflow section Policy: Notify source We haven t dropped it, But won t be doing anything about this for a while. You are best off giving it a go yourself. 10

11 Sales team - respond to RFP New Establish Create RFP team [1] [3] QA In Progr. - Sales - Tech leads - CEO #1 Visibility to sales people, often multitasking #2 WIP limits can be difficult to review #3 Also works as ready buffer for Create RFP 11

12 Sales team - from lead to purchase Lead Proposal Writen Under Negotiation Won (verbal ok) Purchase order received - Sales - Tech leads - CEO Sales team John Hot Cold Alice Hot Cold Can help focusing sales effort while opportunity window permits Many opportunities to manage Physical board requires co-location Tintin Hot Cold Key stuff is to make sure won tranforms fast into purchase order received - CEO 12

13 Marketing team Ice (popcicles) Hot (dogs) Idea board / todo Classes of services Small marketing team PR, web, graphics, blog Web Communication Events Releases - CEO - Sales Marketing kanban In Third party Under Validation (well) Ideas repriotitization and aging visible Visual progress of combined work Over administration? 13

14 Now, go practice! 14