Signs saying "Continue doing," "Start doing," and "Stop doing" 5 Tips for Getting Retrospectives Done Right

Unfortunately, many retrospectives are not productive. It may be that the discussions are unfocused, not enough data was gathered to be helpful for analysis, or the team concentrates too much on issues they can’t control. Retrospectives should be a key part of an agile process for helping the team improve. Here are five tips that will help you have more valuable retrospectives.

Marco Corona
Sparkly "2017" sign Top 10 AgileConnection Articles of 2017

Agile software development is mainstream by now, but people are still finding ways to experiment with agile. Measuring agile success with metrics, the debate over whether to use estimates, and improving predictability in Scrum were all hot topics last year. The rise of DevOps has given even more material for people curious to adopt the practice, so automation and "continuous everything" were also popular subjects.

Heather Shanholtzer
Agile estimation points 5 Overlooked Opportunities in Agile Estimation

Agile story estimation gives the team insight into the level of effort for each work item, allows the team to assess each requirement’s relative priority, and lets the team refine and clarify story items. But there are even more benefits that can be gained from the estimation process. Try to take advantage of these five opportunities for growth when your team is estimating stories.

Ajeet Singh
Icon of agile process Using Sprints for Agile Coaching

Discussing the work to be done as a group, building in short iterations, getting feedback, and looking for ways to improve are not just practices for development teams—it is an effective way to achieve any goal. Here, Ben Kopel details his experience of working with other agile coaches in a sprint to hire a new ScrumMaster.

Ben Kopel

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.