In Effective Agility Requires Cultural Changes: Part 1, I said that real agile approaches require cultural change to focus on flow efficiency, where we focus on watching the work, not the people. Too few organizations can do that. But teams can change how they work—in any approach. Here are three suggestions to emulate flow efficiency […]
Do you ever struggle with knowing if you should split stories? Or wondering if you have a valuable minimum? Jeffrey Frederick and Squirrel offered a signal for a too-small minimum in their podcast, MVP Cubed. That signal was when people became bored with the work. Let me add some additional tests: When the team can’t
In our first article — “Stay Agile with Discovery” (May 11, 2016)— we discussed how to use a discovery project to show a non-agile customer or sponsor the benefits of going agile. Now we will focus on building trust with a client who is ready to consider agile approaches. After the discovery project, Martha was ready
Some agile teams build and maintain their project’s rhythm, happily developing the system. Sure, they may encounter issues–but they can manage those problems and they successfully release the product. No one works overtime, the product owner is happy and the users are happy with the system. Then there are the other teams. I meet many