In this episode of The Agile Coach, Vivek and Pabitra will go in-depth with explaining the difference between a Sprint Review and a Sprint Retrospective. Pabitra will be spilling all the juicy details from the definition, to how each of these two activities is executed.

HIGHLIGHTS

• What is a Sprint review
• Observed patterns
• The need for databases
• What is a Sprint Retrospective
• Make the retrospective fun
• It's not a blame game

QUOTES

Pabitra - Defining a Sprint Review:

“Sprint Review really is a more of an informal event that happens into the sprint and is really to showcase what the team has done over the sprint, really the product increment, what did they create.”

Pabitra - The need for databases:

“Even though the stakeholders might not understand the technicality of it, just talking about it and saying, we needed to create this database, or we needed to do this thing on the back end, and now because we have this, here is how it's gonna help.”

Pabitra - Defining a Sprint Retrospective:

“Sprint retrospective is a big deal for the team and also for the scrum master because that's one meeting that you solely are responsible for.

Pabitra - Keep it fresh and fun:

“You want to keep it spicy, you want to keep it fun and engaging, and so definitely restarts, research some things so that you can keep it fresh and keep alternating throughout.”

Pabitra - Don’t make it a blame game:

“We want to talk on how we improve on these different things, but we're not here to blame anybody, and so really putting that up there, it's definitely important.”

Get to know Pabitra and what she’s up to:

• About Pabitra

Connect with Vivek and find out more about what he’s up to:

• About Vivek
• About The Agile Coach
• Agile Coach Website

If you enjoy The Agile Coach and are interested in learning more, you can check us out at the link below:

• LinkedIn: https://www.linkedin.com/company/the-agile-coach-llc