Nov 29, 2016
Teams often lose sight of the business outcomes as they write stories and features in "technicalese", which external users may not be able to comprehend. SPC Stuart Perron thinks that PI objectives are a great way to keep the focus on the results in user language, so they can get quick feedback. Even before the work on the stories begins, stakeholders can rate the value of the completed story or feature. Then again when the story is completed, the team can share the true results and have the stakeholders rate its value, which may be more or less than predicted. SolutionsIQ SAFe consultant Scott Frost hosts at SAFe Summit 2016 in Denver, Colorado. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thought leaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe! Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter Like: http://bit.ly/SIQFacebook