Current agile practices are far too narrowly focused on delivering code to users and customers. There is no systems-wide view of other stakeholders, of databases, and anything else except the code. This article describes what ‘Evo’ is at core, and how it is different from other Agile practices, and why ‘done’ should mean ‘value delivered to stakeholders’.
Customers come to us with a new product idea and they always ask the questions - how long will it take and how much will it cost us to deliver? Reality is uncertain, yet we as software developers are expected to deliver new products with certainty. This article shows how to do planning using reference class forecasting with the #NoEstimates paradigm which promises more accuracy in forecasts.
While organizations operate under an illusion of certainty, tradeoffs are inevitable. Giving up certainty does not mean giving up predictability. This article examines four flow choices for software delivery and presents three choices for IT Delivery: Throughput, Flexibility and all out speed.
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7
In this article, Yogesh Kumar explains how to apply Agile techniques to create and maintain healthy business strategies. This approach can turn good business strategies into great ones. 7
This article ties a rather abstract and developer centered concept (story points) to the real world of business (spreadsheets and ledgers). Making this connection is essential for management. 5
Agile seems to be all about short-term focus and a product life cycle is typically the polar opposite. How does one compare the relationship between the two? This is where product value comes in. 3
Fixed price contracts are often decried as evil, however they are something which many agile teams face. How can a company execute one using agile practices to achieve better results with lower risk? 15
To turn code into working software we need to deploy and test it. Often, we fail to emphasize the latter as well as the former. 2
With Agile adoption, context is everything: this book offers patterns and tools to help determine which practices most contribute to meeting your organization's goals. 2
For developers and leaders only familiar with Scrum or XP, Lean may be a bit of a mystery. Here's an introduction to Lean Thinking and how it enhances software development. 7
Developers and the business use numbers differently, leading to poor communication. Here the "Spirit of Agile" tells a developer the trick: translate non-computational issues into number language. 3