“What should I work on next?”
Yuval Yeret quotes David Anderson:
- Value trumps Flow – Expedite at the expense of flow to maximize value
- Flow trumps Waste Elimination – Increase WIP (work in progress) if required to maintain flow even though it will add waste
- Eliminate waste to improve efficiency – Do not pursue economy of scale
See also Al Shalloway on Lean thinking about waste in software development - it’s not about optimizing and reducing the use of “resources” (to quote a tweet by @drunkcod).
So I don’t have much time for hobby projects… And when I do have time, it is from various computers, with various setup.
That’s why I’m testing the following combination of online services, and so far it looks promising for my needs…
Full utilization is not effective, not efficient, and causes delays
Being busy all the time is bad for you, your team, and your organization. It is far better to allow for slack, which is not a bad thing, but creates opportunities for improvement without needing to schedule them.
“Recipe” for what to work on next, incorporating slack:
- Can you help progress existing planned, started work?
Work on that.
- Can’t do that?
Find bottleneck and help work to release it.
- Can’t do that either?
Do some (improvement) work which
- won’t create any work downstream,
- will improve future throughput, and
- can be paused as soon as existing kanban related work is available.
A bit more reading related to slack.
Denne artikkelen ble først lagt ut på blogg.bouvet.no.
Det finnes mange ulike beskrivelser av Kanban. Er du interessert i å vite litt mer om hva det egentlig er?