Part 1 in a 12-part series. This post covers continuous delivery.
The first principle;
Principles behind the Agile Manifesto
For this series, think of software as products and services. Customers will not pay for crappy products and services, unless they perceive value.
That might come as a shock.
Allow me to provide a comparison. One of the first cars I was allowed to drive is shown below.
One of the first cars I chose to buy is also shown below.
For me, the better value was the Buick. It didn’t matter that the Toyota was a better quality product. At 16 to 17 years-old, I wanted a car that girls would ride in!
Deliver Continuous Value
Let’s redefine the conversation to cover more than just software. I suggest that we look at products and services based on value. Customers care about value and we have to as well.
How do we get to continuous delivery of value? Look at Agile Value #1; Individuals and Interactions.
First, we talk with customers and get their thoughts on value. Next, we create a small sample of what we understand from the conversation. If the sample doesn’t match the customers understanding, we fix it until we get is right. Finally, we adjust and scale to a viable product and service customers will buy based on value.
Yeah, this is a simplified process. No disagreement on that feedback.
What matters is the continuous delivery. Conditions will change. Preferences will change. As long as discussions are frequently happening with customers, we can deliver value and adjust as needed.
This principle is uncomfortable to accept. I struggle with it because I want our team’s products and services to be perfect. The work done doesn’t need to be perfect, just have value the customer pays for.
Principle 1, Principle 2, Principle 3, Principle 4, Principle 5, Principle 6, Principle 7, Principle 8, Principle 9, Principle 10, Principle 11, Principle 12
