Can we satisfy our customers needs in the Digital World
Satisfying your Customers
As the Agile Manifesto states: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Agile believes we don’t know what software should do when we start a project. By satisfying the customer through early and continuous delivery of valuable software, agile teams can start to triangulate into the right software for the customer by giving them something, having them give us feedback, and then shooting closer to the software they’re ultimately going to use and has the most business value possible.
Agile believes we don’t know what software should do when we start a project. By satisfying the customer through early and continuous delivery of valuable software, agile teams can start to triangulate into the right software for the customer by giving them something, having them give us feedback, and then shooting closer to the software they’re ultimately going to use and has the most business value possible.
How Agile Can Help with Customer Satisfaction
Examples of Customer Dissatisfaction with Projects |
How Agile Approaches Can Increase Customer Satisfaction |
The product requirements were misunderstood by the development team. |
Product owners work closely with the customer to define and refine product requirements and provide clarity to the development team.Agile project teams demonstrate and deliver working functionality at regular intervals. If a product doesn’t work the way the customer thinks it should work, the customer is able to provide feedback at the end of the sprint, not before it’s too late at the end of the project. |
The product wasn’t delivered when the customer needed it. |
Working in sprints allows agile project teams to deliver high-priority functionality early and often. |
The customer can’t request changes without additional cost and time. |
Agile processes are built for change. Development teams can accommodate new requirements, requirement updates, and shifting priorities with each sprint, offsetting the cost of these changes by removing the lowest-priority requirements — functionality that likely will never or rarely get used. |