I attended a Certified ScrumMaster training class this year delivered by Lithespeed. The class was very valuable, and I want to share a tool, trade-off matrix, to help set customer and team expectations. In my opinion this is a tool that should be used on all projects early in the planning stage. Here is an example of a trade-off matrix.
All 30 Use Cases Identified
2 Large Bugs per month is acceptable
By documenting this at the beginning of a project, the project sponsor and all project stakeholders (including project team members) have a clear view of what project success looks like. In the example above success is implementing all features, within a budget close to $500k and somewhere within 3-6 months. In addition the sponsor is OK with 2 large bugs a month.
You may find that a project sponsor wants everything “Fixed.” By using this matrix to illustrate the triple constraint it helps drives your discussion explaining why there needs to be a trade-off.
I plan on using this to help define success. Please share any tools you use.
- #AskAnAnalyst Podcast Episode 26: Are BAs Becoming Obsolete? - February 28, 2017
- #AskAnAnalyst Podcast Episode 25: State of Agile - February 7, 2017
- #AskAnAnalyst Podcast Episode 24: An Agile Mindset - January 27, 2017
- A Monthly Guide to Becoming a Better Business Analysis Professional - January 11, 2017
- #AskAnAnalyst Podcast Episode 22: Business Analysis in 2017 - January 10, 2017
- #AskAnAnalyst Podcast Episode 21: Business Analysis in 2016 - December 8, 2016
- #AskAnAnalyst Podcast Episode 20: Effectively Give and Receive Feedback - November 15, 2016
- #AskAnAnalyst Podcast Episode 19: Live from #BBCCon - November 3, 2016
- #AskAnAnalyst Podcast Episode 18: More Business Analysis Basics - October 4, 2016
- #AskAnAnalyst Podcast Episode 17: Back to Business Analysis Basics - September 13, 2016