Happiness Metric | Glossary

Definition:

The Retrospective meeting is the “Check” part of Plan-Do-Check-Act cycle where key is getting to that “Act” step, that kaizen which will actually change the process and make it things better the next time. It’s not good enough to share how you feel, you need to be able to act. The best way is to capture all this with what is called “Happiness Matric” which is a very effective way of getting at what the kaizen should be, and also which kaizen will make the people the happiest.

Each person on the team answers few questions on a scale of 1 to 5, about how they feel about their role in the company, how they feel about the company as a whole, why do they feel that way, what one thing will make them happy in upcoming sprint? With these questions in a few minutes every person on the team sparks an insightful conversations. This method exposes what is most important for each team member and what they think is most important for the company.

Happiness Metric is a leading indicator which helps in visualizing the aspects that matters most to the team

Further Reading:

Book: Succeeding with Agile Software Development Using Scrum by Mike Cohn
Book: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland

Conditions of Satisfaction | Glossary

Definition:

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