Change for Free | Glossary


Companies now prefer to deliver high value features. Company commits to deliver high quality product defined by the agreed upon Definition of Done. Customer participates actively with Scrum team, keep himself available and engaged during the entire project.

Customer shall be able to make changes to the Scope without incurring any additional cost if total Scope of contracted work is not changed. New features may be added for free at Sprint boundaries if items of equal scope are removed from the contract.

The customer is expected to be active in the project prioritizing features by business value and get it implemented in order to get maximum value, participate in each sprint planning by discussing selected features with team answering question to provide clarification. Participate in writing conditions of satisfaction for each feature so that the team has the clear definition of done. At sprint reavie provide feedback for both work-in-progress and completed work. He also participate responsibly in grooming the backlog where high value items are swapped with comparative low value items.

Further Reading:

Book: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland
Book: Succeeding with Agile, Software development using Scrum

Conditions of Satisfaction | Glossary


For whole release as well as feature or story there are conditions of satisfaction which helps to define the story acceptance. Development team can’t successfully deliver the business wants unless conditions of satisfaction for a story are agreed up front.

The Customer team should “speak with one voice”, if team is getting different requirement from different stakeholders, team needs to push back  and put off the story until there is a firm list of business satisfaction conditions. The best way go understand customer’s requirements is to talk with the customer face to face. These conditions are based on key assumptions and decisions made by customer for a story coming with a high-level acceptance criteria for each story.

Discussing conditions of satisfaction helps identify risk and increases the team’s confidence in writing and correctly estimating all of the task that are needed to complete the story

Further Reading:

Book: AGILE TESTING A Practical Guide for Testers and Agile Teams
Book: Effective Software Project Management by Robert K. Wysocki