CategoryAgile

100% utilisation myth and slack time

1

In my recent blog post I covered a topic of limiting Work in Progress. I briefly mentioned that in many companies working on many tasks in parallel is somehow more important than accomplishing them. 100 utilisation myth Many organisation believe that their employees should always be busy with work which results in aiming for their constant 100% utilisation. At first glance it may sound reasonable...

Limiting Work in Progress

L

In many organisations being busy is valued more than delivering the results. At first sight, it may sound quite reasonable – after all, we’re all paid for having hands full of work, aren’t we? Unfortunately, it doesn’t work that way. In a vast majority of cases, the more tasks we try to complete, the less we really accomplish. And pushing yourself to work even harder...

Agile Assessment

A

Many organisations and teams that adopt Agile come to the point when knowing how agile they are becomes an important question. It’s especially important when first stages of Agile transformation prove to be successful, teams finally work at a sustainable pace and it becomes more difficult to identify obvious areas for further improvements.

Relative Value Points

R

Product backlog should be DEEP – detailed appropriately, emergent, estimated and prioritised. Everyone who learns about Scrum should be familiar with these key attributes of a good product backlog. But how is the product backlog ordered? Well, most Scrum practitioners would probably say that it’s Product Owner’s decision, but the business value seems like a fair attribute to be...