Comments on: Optimize iteration length for feedback https://www.robg3d.com/2014/06/optimize-iteration-length-for-feedback/ Blog of Rob Galanakis (@robgalanakis) Thu, 05 Jun 2014 13:27:21 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Rob Galanakis https://www.robg3d.com/2014/06/optimize-iteration-length-for-feedback/#comment-230051 Thu, 05 Jun 2014 13:27:21 +0000 http://www.robg3d.com/?p=1510#comment-230051 Retros may be the most important structural component of staying Agile. Without the ability to retrospect well, you cannot get feedback, and (as you identify) you cannot improve. Of course you still need to be able to *act* on that feedback, but you need good retros to get it.

]]> By: Jon Lauridsen https://www.robg3d.com/2014/06/optimize-iteration-length-for-feedback/#comment-230047 Thu, 05 Jun 2014 11:24:12 +0000 http://www.robg3d.com/?p=1510#comment-230047 Yep, well put.

One peeve of mine is when retros are flaccid. If your retro consists of only good things and/or complaints of “other teams need to do better to not cause problems for us”, then something is plain wrong. It’s exactly this time you need to be collecting and verifying feedback. Failure here stops the wheel of continous improvement, so it’s on you to be critical and on the ball! Challenge yourself to find areas to optimize.

Sometimes I think retros are the most important part to stay agile, though of course it’s not as simple as that :)

]]>