Change for Free | Glossary

Definition:

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

Role-Feature-Reason | Glossary

Definition:

Role-Feature-Reason is a template used by Product Owners, Team members and other stakeholders who is gathering requirement as User Stories .

Requirement written with this template describes the right objective from users perspective. This helps to understand the feature, how the actual user will utilise that feature, how he benefits.

As a [type of User] I want [some feature] so that  [some reason]

The role (Who) The feature (what) The reason (why)

As a account holder, I want to check my balance online, so that I can do a purchase.

This template used in Agile Software Development helps to capture the requirement of a software feature. Helps the requirement to evolve and is supposed to aid in future conversation to pay attention not just to “what” the desired software product is to do, but also “from whom” it does matter and for “what objectives”

Further Reading:

Book: User Stories Applied: For Agile Software Development by Mike Cohn
https://www.agilealliance.org/glossary/role-feature/
http://codesqueeze.com/the-easy-way-to-writing-good-user-stories/