useless defensless process

When you don’t have an answer for why a process is there

“Individuals and interactions over processes and tools” – this is the first value in the Agile Manifesto.

The. Very. First. And yet we somehow manage through the frameworks that actually were born as a result of the manifesto, to put more emphasis on the latter.

Just like you challenge every feature request, challenge every process. Is it truly helping the team? Or is it there because “that’s how we’ve always done things

via Michael Lopp

 

Force transparency, and get accountability for free

Get accountability for free

Force is quite a strong word and sometimes bears a negative shade to it.

However, the underlying principle is good. If the work environment is set up so that teams can communicate their progress, accountability comes as a natural consequence.

This point is particularly important when building a minimum viable product. Two images come to mind:

How to build a minimum viable product

and this

Minimum viable product

Quote taken from Brandon Chu’s “7 Heuristics for being a product director”.