Rotting fruit: what an IT operations team learned from Kanban
· Wim Kerkhoff · Dispatch
Rotting Fruit
On the weekend I stumbled upon this YouTube video of how an IT Operations team used Kanban to improve their world for Project and Service delivery. Great ideas and different ways of looking at old problems. It’s about 30 mins long and includes a walk-through of a real life (sticky notes on the wall) Kanban board that they custom designed.
My favorite quote is “too much work, and work stated but not moving, is like rotting fruit: it’s expensive and smells bad!!”
The video is here: https://www.youtube.com/watch?v=coRx-onQ09Y
And their slickdeck is here: https://www.slideshare.net/ITRevolution/wednesday-415-dominica-de-grandis-gb-final
There is a lot of good info in it… it’s from a DevOps conference, and I think MSPs can learn a lot from the Agile (working in short cycles and adjusting as you go; it suits service and project teams, not only software)/DevOps world. Here are two of my favorite slides:
What randomizes your day?
- Conflicting priorities
- Changing priorities
- Interruptions
- Context switching
- Unable to meet commitments
Top 5 reasons why people take on more work then they have capacity to do:
- Hard to say “no” to people we like
- Don’t want to let the team down
- Didn’t realize work would take so long
- Fear from those in position of power
- People pleaser
Hope this was useful – let me if it was, or wasn’t…