Last Retrospective with Team

[K. Thomas]

Hi all -

I'm wrapping up my first scrum project and wanted some advice on how
to plan for our last retrospective together. Usually, our
retrospective involves having all team members call out what made them
mad or glad about the last sprint. We then vote and together come up
with a way to mitigate this being an issue in any future sprints. We
also vote on the Scrum Values just to get a read on how we did and as
well to remind us all of what they are.

I wanted to figure out the best use of our teams last retrospective
since the team is disbanding and moving onto other projects. I was
thinking of doing the same this time as well as showing all of the
previous retrospective outcomes. I also thought I could share our
velocity, our story time to life, and the final graph of our values
over the past 13 springs. Then we'll be heading out to a local bar to
celebrate.

Would love to hear what do other SM do for their last retrospective.
Any thoughts or suggestions on what I have planned?

-Karen

[Mark Levison]

Hmm - you mean they're not keeping the team together? Why waste an excellent high performing team? Why spend all that money to rebuild one on another project.

Sad. The team won't exist anymore so there is nothing useful to improve except teaching the company how to keep teams together. Instead of a retrospective (who's purpose is to improve) I would go to a pub and hold a wake.

Cheers
Mark Levison

Mark Levison | Agile Pain Relief Consulting | Certified Scrum Trainer
Agile Editor @ InfoQ | Blog | Twitter | Office: (613) 862-2538
Recent Entries: Story Slicing How Small is Small Enough, Why use an Agile Coach

[7thpixel]

You may want to wrap up with an Appreciations Exercise.

It would seem a fitting end (although wake idea is growing on me)

--
David J Bland
Scrumology | Enabling Agility
http://www.scrumology.net

--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To post to this group, send email to scruma...@googlegroups.com.
To unsubscribe from this group, send email to scrumallianc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.

[K. Thomas]

I should of been more specific. The developer, the Prod Owner and me,
the SM are staying and we'll be responsible for maintenance work. The
BA, QA and one developer are not. I work in a non-profit so resources
are scarce and are shared across teams. I'm looking into using Kanban
(or a Scrumban) for the maintenance work. I hope that I'm able to
continue some of the momentum created during this project.

Funny you should mention a wake since I have had a funeral for a
horrible project a number of years ago. Needless to say it was not run
with scrum!

On Mar 30, 2:12 pm, Mark Levison <m...@mlevison.com> wrote:
> Hmm - you mean they're not keeping the team together? Why waste an excellent
> high performing team? Why spend all that money to rebuild one on another
> project.
>
> Sad. The team won't exist anymore so there is nothing useful to improve
> except teaching the company how to keep teams together. Instead of a
> retrospective (who's purpose is to improve) I would go to a pub and hold a
> wake.
>
> Cheers
> Mark Levison
>

> [image: Mark] <http://www.flickr.com/photos/36331075@N00/3833840021/>*Mark
> Levison* | Agile Pain Relief Consulting <http://agilepainrelief.com/> |
> Certified Scrum Trainer
> Agile Editor @ InfoQ <http://www.infoq.com/about.jsp> |
> Blog<http://www.notesfromatooluser.com/>|
> Twitter <http://twitter.com/mlevison> | Office: (613) 862-2538

> Recent Entries: Story Slicing How Small is Small

> Enough<http://agilepainrelief.com/notesfromatooluser/2010/09/story-slicing-h...>,
> Why use an Agile
> Coach<http://www.notesfromatooluser.com/2009/11/why-use-an-agile-coach.html>