{"id":191984,"date":"2019-06-09T12:01:11","date_gmt":"2019-06-09T06:31:11","guid":{"rendered":"https:\/\/staging-imarticus.kinsta.cloud\/?p=191984"},"modified":"2021-03-10T07:54:46","modified_gmt":"2021-03-10T07:54:46","slug":"knowledge-center-agile-business-analysis-retrospectives-make-better-product-outcomes","status":"publish","type":"post","link":"https:\/\/imarticus.org\/blog\/knowledge-center-agile-business-analysis-retrospectives-make-better-product-outcomes\/","title":{"rendered":"Retrospectives Make Better Product Outcomes"},"content":{"rendered":"

Most product managers and coaches struggle with frustrating outcomes. The answer to such a situation lies in the retrospectives<\/em>.<\/em> The Retrospectives-tool is an essential of the PMs toolkit and relies on learning, transparency and exploring curiosity in a safe environment. The product retrospectives can transform product processes, improve products, and offers an opportunity for continued learning through the iterative product development life-cycle.<\/p>\n

Why Retrospectives?<\/h3>\n

The retrospective generates actions based on consensus and produces new information unlike the regular meets reviewing past performance, data and actions.
\nIt is a based-in-reality change and action process which can be undertaken to occur at regular intervals. For example the quarterly review of road-maps, the finish of a sprint iteration, after a release, sales \/client meeting, product launch or the hypothesis-testing. The retrospective reviews what, how and why in terms of reviewing over a fixed timeframe the desired outcome or event and comprises the entire product development community of stakeholders, customers, product and development teams.
\nThe accruing benefits:<\/strong>
\nThe retrospective is beneficial when it is able to:\u00a0<\/strong><\/em><\/p>\n