1. Kanban in Practice
Randy R. Johns, PMP MBA
Manager, Operations Applications
Drummond Company, Inc.
8/21/18
2. About Me
•Manager, Operations Applications (OA)
•Operations and technology hybrid experience
• PMP – Dec 2012
• MBA – Oct 2015 (PM Concentration)
3.
4. Drummond Company and MIS
•Multinational organization working in mining, real
estate, minerals processing, and heavy industrial repair
and fabrication
•Microsoft shop with PMI-driven project processes
•OATeam of 9
• 5 developers
• 4 Business Analysts
5. OAWork Management
•Types of work
•Is the process the same for support or new development?
•Historically a waterfall project environment…so what?
•Could we do better?
Reported Issue
or New
Development
BA Analysis
with Developer
Development Quality Testing User Testing
Approvals and
Documentation
Implementation
8. The ArticleThat Changed Everything
•Can two pages have a big impact?
•Whiteboard and sticky notes to the rescue!
•Time to learn more!
9. Kanban Defined
•“A Japanese manufacturing system in which the
supply of components is regulated through the use
of an instruction card sent along the production
line.”
•“Signboard”
10. Tenants of Kanban
• Visualize your work
• Limit your work in process (WIP)
• ‘Pull’ system of work
• Don’t change anything you’re doing right now
• Stop starting and start finishing
15. My Kanban Board Evolution
•I love a good whiteboard a fresh set of Expo markers
•I was already doing it…sort of
•Handwritten with pinstripes to vinyl letters and a ruler
•Finally…digital!
23. My Board – Card Detail
• Card color
• Yellow = Project
• Green = Support Item
• CardTitle (project or support item)
• Colored Dot = Status (visual indicator)
• % complete slider
• Assigned resource(s)
• Comments (history of comments is kept)
• Application name
• Location
• Due date
• Left side bar color = severity/priority
25. Impacts of Kanban
•No changes to current processes or roles
•Almost immediate insight to overall workload
•Bottleneck visibility
•Engaged team
• All work is visible and in many cases, resources can choose
their next assignment
•More accurate resource / capacity planning
26. Next Steps
•Metrics / Analytics
• How well did we do on that task/project/support item?
•Engage management in resource planning
•Simplified reporting
• Task
• Backlog
• Progress
•Using Kanban for a small development project
Mention PMICAC involvement
Add PMICAC information for Montgomery presentation
Received Kanban How To from Mark 1/30/18 simply because I had purchased a new and larger whiteboard.
It starts with your brain.
A picture is worth a thousand words for scientific reasons:
The brain processes visual information 60,000 times faster than text. 40 percent of all nerve fibers connected to the brain are linked to the retina.
Visual information comprises 90 percent of the data that comes to our brain, suggesting that our neurological pathways might even prefer pictures over text.
Kanban helps you harness the power of visual information by using sticky notes on a whiteboard to create a “picture” of your work.
Seeing how your work flows within your team’s process lets you not only communicate status, but also give and receive context for the work.
Kanban takes information that typically would be communicated via words and turns it into brain candy.