The Bradley User Story Maturity Model is not intended as a predictor of success, by any means. It is simply meant as a way for teams to assess and improve their usage of the practice.
  • In particular, if the PO is not doing a good job prioritizing or gathering requirements, then the team might suffer really bad consequences even though their User Story Maturity is high.
  • On the flip side, if the developers are not good at delivering stories that pass the story tests and/or getting PO signoff, then the team might suffer really bad consequences even though their User Story Maturity is high.
  • I'm sure numerous other examples of this exist, so be forewarned!

Back to the model