Back to Forum

Help Staying Sharp

Last post 07:13 am November 9, 2017 by Julian Bayer
2 replies
Jamie Craig
01:20 pm November 6, 2017

Our team is in a good position and does well sprint to sprint.  We hit pitfalls like anyone else, but we continue to produce.  I am looking for retrospective ideas besides Anchors/Sailboats (which the team is tired of) to review/discuss the past sprint or at least to keep the team thinking of ways to improve.  Small games/exercises would be good.  Anything for a small team of 5 to 10.  I would like something that puts the Dev/QA side in the position of BA/Product owner and the reverse. I would do this during the Sprint planning. 

Thanks in advance for the suggestions!

Ian Mitchell
08:31 pm November 6, 2017
Julian Bayer
07:13 am November 9, 2017

Also http://www.funretrospectives.com/ has some good ideas.

The book "Agile Retrospectives: Making Good Teams Great" by Esther Derby and Diana Larsen has lots of activities for different kinds of retrospectives.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.