Most Agile software methods operate under the key assumption that resources (software developers and testers) are interchangeable, just as user stories are independent of each other. This is one area where Agile software experts run into real trouble when they push these ideas onto hardware teams.
To Accelerate Net-Zero, Commit Early but Decide Late
A growing number of major companies are following the lead of Amazon, Microsoft, and Google to set aggressive targets for achieving net zero carbon emissions in their businesses. To hit those commitments, companies need to make important decisions about where to focus the time, energy, and money they have to invest in sustainability. It may […]
Why Agile Hardware Development
An Agile Software Development team works iteratively — they write some code or make a UI design model, get fast feedback on it, improve it and add to it. Some people claim that 3D printing and other rapid prototyping methods allow hardware developers to work just as iteratively. But they are wrong, for two reasons.
3 Reasons Why Good Decisions
Can’t Be Scored:
Why numbers lead teams astray in their most important decisions —
and what to do instead.
When my partner and I were driving through the Luxembourg countryside, we enjoyed the beautiful sights: scenic mountains with hilltop castles and lush forests. As night began to fall, the fog descended. At first, it was beautiful. Then visibility became more and more restricted. Relaxation turned into apprehension as we realized the increasing danger on […]
How Teams Can Find Focus, Even When They’re Overwhelmed:
Find your NUDs — those things that are New, Unique or Difficult — to find your focus
Recently, my thinking about Key Decisions has changed. I used to think that teams needed to address all their high impact/high unknown Key Decisions and that teams could be trusted to come up with the right ones within a few cycles of re-planning, even if they struggled during the integration event.