Even in its simplicity there are a few similarities (lessons?) with the real-world that I think are worth mentioning:
- Generalists (like the founder) are often useful because they're able to consume different types of work from the backlog as needed (when flow isn't perfect and work piles up in some areas)
- Ideally work doesn't pile up in any area, and it proceeds left to right without any waiting
- But if you don't want work to wait, you'll have people waiting (the aim should never be 100% utilisation)
- Work going backwards (bugs!) is more expensive (time consuming) than doing it right the first time
- Managing all this isn't easy: it's much better when the team can be proactive and do the right things at the right time without supervision/overhead (having everyone on the same page, shared vision, practice, etc)
Thanks for some good fun… and a reminder of all these things.
Cheers Ivan. That’s exactly what I was hoping it would show.
There’s no cross-skilling available at the moment (I want to add this to the store) but that would demonstrate the value of cross-disciplinary team members.
Even in its simplicity there are a few similarities (lessons?) with the real-world that I think are worth mentioning:
- Generalists (like the founder) are often useful because they're able to consume different types of work from the backlog as needed (when flow isn't perfect and work piles up in some areas)
- Ideally work doesn't pile up in any area, and it proceeds left to right without any waiting
- But if you don't want work to wait, you'll have people waiting (the aim should never be 100% utilisation)
- Work going backwards (bugs!) is more expensive (time consuming) than doing it right the first time
- Managing all this isn't easy: it's much better when the team can be proactive and do the right things at the right time without supervision/overhead (having everyone on the same page, shared vision, practice, etc)
Thanks for some good fun… and a reminder of all these things.