value using Kanban Prioritizing customer Making the most with scarce resources PM Fair 2018

Transcription

1 2018 Prioritizing customer value using Kanban Making the most with scarce resources PM Fair th October

2 Some of My Passions Agile trainer and coach IT Project Manager Columnist, blogger Former President of PMI Denmark Chapter Part of PMI s global agile taskforce in 2015 Reviewer of PMI s Agile Practice Guide (on its way in

3 Debrief and key take-aways The Kanban Method the ultra short version Hands-on work with upstream Kanban Optimizing by climbing Kanban s Maturity Ladder Upstream and downstream Kanban 2 3 Focusing on prioritization principles 3

4 Before we start, I want to ask you something: Did you ever experience Bad requirements? Bad prioritization done by your management? More work than your team had the capacity to complete? Unrealistic deadlines? Do you have any practical experience with the Kanban method? What do you hope to take back from this workshop? th October

5 1 The Kanban method: An ultra-short walk-through 5

6 Kanban controls work not people. You build your Kanban system so it fits your context Kanban can be used for all kinds of knowledge work 6

7 Why use Kanban to control your team activities or projects We visualize invisible work, and we have stopped multitasking. Our tasks flow faster No competing backlogs! All our work is in our Kanban system and prioritized systematically Just a glance at our board we get a clear, common view of how our project is doing There is no wishful thinking in Kanban! 7

8 The 3 agendas and 9 values in Kanban 1 Improvement 2 Service Transformation 3 Organizational Change Transparency Balance Collaboration Customer focus Flow Leadership Understanding Agreement Respect th October

9 The Three Change Management Principles in Kanban 2 1 Start with what you do now - Understanding the current processes, as actually practiced - Respecting existing roles, responsibilities and job titles 3 Gain agreement to pursue improvement through evolutionary change Encourage acts of leadership at every level in your organization from individual contributor to senior management th October

10 The 6 general practices (the how-to ) in Kanban Visualize Limit Work in 1 Manage flow Progress Improve collaboratively and evolve experimentally 5 Implement feedback loops 4 Make policies explicit 10 10

11 2 Upstream and downstream Kanban 11

12 A downstream example: using the practices Class-of-service 1. Visualize 2. Limit work in progress Work Item Types Queue Break-down Analysis Development Quality Assurance Ready to deploy / Done Ongoing Done Ongoing Done Ongoing Done Development 4 Expedite Error correction 3 W/deadline Support / maintenance Ad-hoc tasks 2 1 The expedite lane and the red stickies serve the same purpose 3. Manage flow Standard Expedite 4. Make policies explicit Intangible Other Info Project allocations On call: Mon. Tue. Wed. Thur. Fri. Tasks 0-30 min. Tasks min. Externally blocked Internally blocked Urgent Policies ~~~~~~ ~ ~ ~ ~ Policies ~~~~~~ ~ ~ ~ ~ Policies ~~~~~~ ~ ~ ~ ~ Policies ~~~~~~ ~ ~ ~ ~ 12 12

13 Slut med to-dolister Kanban på projekter Risici visualiseres Den røde kasse = det område, hvor vi kan kontrollere i gangværende arbejde Jeg ved nok til at kunne bedømme om min leverandør leverer som aftalt Det ugentlige højdepunkter 13 13

14 Upstream and downstream Kanban Service Request Manager (SRM) + Service Delivery Manager (SDM) Pool of Ideas Upstream Kanban Risk Analysis Requirements Analysis Ready for development Downstream Kanban Development Testing Committed Ongoing Done Verification Done Min & Max limits ensure sufficient options are always available K L J I H D C B E A Options SRM F SDM Committed Work $$ spent acquiring options $$$ spent converting options O P Q Reject 14 14

15 3 Focusing on prioritization principles 15

16 In your upstream Kanban you must decide how to determine what is most important Pool of Ideas Upstream Kanban Risk Analysis Requirements Analysis S R Options P $$ spent acquiring options O N Q M Ready for development L K SRM Reject What are your scarce resources, and how should you prioritize your activities? Is risk a factor that you have to take into consideration? Is price or time something you have to consider? Is the best possible use of resource bottlenecks the most important prioritization criteria? Is it the most important project that you must prioritize first when you prioritize your tasks? 16 16

17 4 Hands-on work with upstream Kanban 17

18 Discuss with your team: You have 20 minutes 1. Think about your project (or one in the past): How do you currently prioritize the work that needs to be done? Do you see elements of randomness? 2. How might the Kanban way of prioritizing help you on your projects? 3. Who would you involve, when you do the prioritization? 4. Who would be your Service Request Manager? 5. Suggest how you would build your upstream Kanban board for a team of 6 18

19 5 Debrief and take-aways 19

20 Each team has 5 minutes to present their results First, each team presents their upstream board: explain how you reached this result Based on the results from your team work, how does an upstream Kanban board differ from what you do today? Also explain if/how this way of prioritization might help you on your projects th October

21 Key take-aways Even if you don t use the Kanban method for your project, you can use upstream Kanban techniques for prioritization With Kanban you can ensure that the most important activities are done first Working with upstream Kanban principles, you will ensure rigid prioritization based on whatever are your scarce resources Of course all of this will only happen if people respect these processes and the agreements made concerning prioritization principles Your ability to involve the right people and facilitate decision-making based on mutual agreement will influence project lead times th October

22 Contact information xvoto.wordpress.com You can also reach me via LinkedIn, Twitter, and Facebook 22

23 THE END? 23 23