SHE QC
SHE QC is a Software Engineering ideation technique to refine requirements. SHE QC as a process discusses how teams could structure the requirement discovery session with the product owner to come up with detailed acceptance criteria.[1] The process uses elements of the design thinking as a tool to trigger conversation and also uses Specification by example[2] to document the acceptance criteria. SHE QC grooming technique is typically used in the Agile teams who want to groom stories more continuously i.e. on a daily basis. The primary motive of this technique is to structure & time-boxed grooming discussions, also called as 3 Amigo discussions [3]
Introduction
The SHE QC style of grooming is a technique for refining and slicing complex stories. It’s highly structured & time-boxed approach claims to enable teams to trigger the right conversation and thus craft the correct acceptance criteria.
SHE QC an acronym
SHE QC is an acronym for[4]
S for Sad scenarios
H for Happy scenarios
These are basic scenarios identified without much effort if you have a great Product Owner (PO)
E for Exceptional
scenarios we typically don’t anticipate.
Q for Quality
scenarios related to quality attributes or Nonfunctional requirements like performance, reliability, availability, etc
C for Constraints
stands for Constraints pertaining to system constraints. These constraints could be architectural, infrastructure constraints or even team level constraints
The Process
Explore
First ~5 min, Product Owner explains the story with basic scenarios which would cover most of the happy and sad cases. She also emphasizes the value of the story.
Discover
Next ~15 min, discussions are focused to carve out more scenarios that the PO might have missed out; the scenarios are written down bucketed under different scenario types. Quantity over Quality
Uncover
In the next ~15 min, we iterate over each scenario type with an objective to cover scenarios that we might have missed. We do this by focusing only on a type of scenario for a focused time (time-boxed) for example exceptional scenarios for 3 min then quality scenario and so on. This approach gives the team to narrow their focus and think in that scenario dimension. One should keep in mind that we don’t shoot down any scenarios
Converge
The next ~10 min we identify the Must Have Scenarios (MHS). Currently, there is an explosion of scenarios. Identify the right minimal set of scenarios. The MHS is across different types and not just happy and sad Remove scenarios we don’t want to build. Rest of the scenarios are grouped and pushed back to the backlog.
Criticism
It was also noted that SHE QC style of grooming was ineffective and counterproductive for distributed and dispersed agile teams. The use of SHE QC style of grooming is also ineffective and time consuming when the requirements are simple.[5]
submitting for review
This article "SHE QC" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:SHE QC. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
- ↑ "SHE QC A story grooming technique". confengine. Scrum Alliance ,Regional Scrum Gathering Hyderabad. Retrieved 10 February 2019.
- ↑ Gojko, Adzic (2011). Specification by example: how successful teams deliver the right software. Manning Publications Co. ISBN 9781617290084. Search this book on
- ↑ Armour, Phillip G (2000). "The five orders of ignorance". Communications of the ACM. 43 (10): 17–20. doi:10.1145/352183.352194.
- ↑ "the-art-of-crafting-high-performing-teams". Agile Alliances. XP2019.
- ↑ "Behavior-Driven Development: Simplifying the Complex Problem Space". SolutionsIQ. Retrieved 2019-10-09.
