-
Just Enough Kanban
4–7 minutes
One of the most helpful things you can do when facing a problem is to visualize the situation. In software or service delivery, kanban is a handy method that lets teams visualize and better manage their business or workflows. If you don’t know what else to do, make it visual. Find some way to make
-
Mapping Options Using a Risk-Value Matrix
5–7 minutes
When it comes to dealing with all of the things competing for your attention, one habit I’ve picked up from practicing Getting Things Done for over ten years is to start writing down everything that’s on my mind and putting it all into an Inbox. The people I work with always have more work to
-
Limiting how many stories or tasks can occupy any particular activity in a team’s flow is a commonly recommended practice for teams using kanban systems. This way, the team can avoid overloading their system, reduce multitasking, and improve focus and quality. Applying work-in-progress (WIP) limits to kanban systems at the story or task level reveals
-
The Power of Predictable Delivery
7–10 minutesWith most of the Agile teams I’ve been exposed to, I’ve noticed that they spend easily over a hundred person-hours every month on practices like updating plans, reporting metrics, estimating, and sharing status updates. To them, these are some of the core practices that make them Agile. In general, as a way to be less
-
Manage the Value, Not the Work
5–8 minutes
Do you think of software development as an exercise in identifying the right problem, doing the right analysis and getting the right people to code the right features? Or is it more of a discovery and learning activity where you make a bet, build something and get feedback? In the former approach, organizations will create
Flow Focused 