(2018-07-20) Jeffries How To Impose Agile

Ron Jeffries: How to Impose Agile: ...with survival at stake, going “Agile” would be necessary

If they don’t want to go Agile, well, I have no choice.

we’re going to build everything with small teams

Every product team will be responsible for having a ready-to-ship, integrated, working, tested product all the time, containing all the solutions that the team has chosen to be in the product.

We’re asking for running, tested, shippable software every two weeks, delivering what you set yourselves to deliver two weeks ago. It does happen that I only know one basic way to do that, with cross-functional teams with all the needed capabilities to do the job. It does happen that I believe those teams will find comprehensive unit and acceptance tests to be key, that they’ll want to learn to evolve their designs smoothly with refactoring that they’ll need to keep their systems integrated all the time, and so on.

Since we’re setting a two-week planning and review cadence, you may want to consider adopting process elements that are conducive to that, and you’ll likely find them in the “Agile” thought space. I’m sure you will be able to find many ways to do that, and can point you to some options if you need them. But you are absolutely free to use any process you want, so long as you’re giving us what we need: a clear product view, and shippable product every two weeks.