Základné a nadstavbové vzdelávacie programy pre tím.
Dlhodobá podpora tímov mentormi.
Spoznajte potenciál pre zlepšenia tímu.
Príprava a nastavenie tímu pre tvorbu komplexných produktov škálovaným Agile.
Ucelený a zmysluplný rozvoj tímu
Základné a nadstavbové vzdelávacie programy pre Scrum Mastrov.
Dlhodobé programy rozvoja schopností.
Identifikujte svoje potenciály pre ďalší profesionálny rozvoj.
Príprava Scrum Mastrov pre prácu v škálovanom Agile.
Pripravte sa na prácu produktového vlastníka škálovaného portfólia produktov.
Základné a nadstavbové vzdelávacie programy pre Produktových vlastníkov.
Dlhodobé rozvojové programy pre zavedenie agilných praktík do firmy.
Hodnotenie agility firmy a identifikácia potenciálov pre ďalšie zlepšovanie.
Príprava firmy pre škálovanie agilných praktík.
Vzdelávanie pripravujúce firmu pre zavedenie Agile.
Domov / Blog / Why is sprint review important. Make your sprint review great
This article has been published on ScrumDesk product pages.
In the last week, I attended a couple of sprint review sessions. Some of you maybe call them sprint demo. Ok, simply to say, the meeting at the end of the sprint where you are supposed to show your sprint’s achievements. In my case, all sprint review sessions had something in common. People were missing.
In Scrum, the sprint review is a session that closes a sprint (10-15 days iteration) in which completed functionality is demonstrated to the client’s representatives. Very often such a review is called Sprint Demo because it is suggested to provide that information in form of a live demonstration showing completed functionality.
For the business, this is definitely different compared to the previous, waterfall-like process. They see the results very often and regularly, which helps to adopt the product according to changes on the market constantly.
In ScrumDesk we help with agile transformations as well. We found that such a demo is nice at the beginning of an agile transformation, important information is, however, still missing for the business. Working in the sprints doesn’t give you a whole picture of the product status. Being the business you definitely need to understand a wider context than just a sprint.
Therefore after a few sprints, we guide agile teams to do sprint review and not just the demo part.
But still, people are very often missing in the sprint reviews….
Let me ask you a question. What do you think about your IT? The answers we often hear from the business side are:
Maybe you are correct but let me ask you another question. When was the last time you gave IT your ears? Good agile teams want to be proud at the end of the sprint. They want to show you their work and real results.
What good agile teams want the most is your feedback.
If you are not at the sprint review session, there is no feedback. If there is no feedback, no emotion, there is no motivation.
If there is no motivation, there is just a job. If there is ‚it is just a job‘ mindset, there is no creativity. If there is no creativity, there is just an average product.
The average product means business declining in a long term. That means additional pressure on you, dear business. Now you have to „fight“ for your rights and work with the unmotivated team that is doing exactly what you want, will not do anything you did not ask.
You have to write 100% requirements that IT is going to analyze for weeks just to have arguments for upcoming war tension. Meanwhile, your business is going to change once again (even earlier than expected), but hey, you are just arguing about analysis.
Who lost? Everybody. Every person in a company. But especially your clients.
Just because you did not have time, you were in another meeting, you did not pay attention, you did not provide honest feedback.
Sprint review is not just a session for you ScrumMaster or Product Owner, and it is not the session of the team for the team itself. Sprint review is the session with real faces representing the business.
Sprint review is a moment of truth, honesty, shame, and proudness.
Once the sprint itself and the sprint review session is done fine, you will leave the room with engaged, satisfied with your work. That can’t be achieved via training or coaching.
The satisfaction will come in sentences of recognition, honest feedback, claps of hands. That way you will know how you change the world and not just spend another 8 hours (at least) of your lifetime.
Do you often say: „They are not coming to our demo, why we should run it?“. The answer is not THEM. The answer is about YOU.
Great demo invites people for the next sessions. It if is boring or nobody understands what you say, they will never come back. They do not want to lose a lifetime similar to you.
Make it entertaining, funny, unique, human and they will come back. Give them crisp information. Surprise your audience. Satisfy them. Invite them into the conversation. Do not just broadcast.
Start before the sprint planning session. Yes, you read that correctly. Before the planning, the Product Owner should imagine a sprint review session and especially the opening.
Which 3 goals you want to aim in the sprint for?
These three goals will be fulfilled by multiple backlog items. The most important can be recognized upfront so the Product Owner can even guide team members on which user stories will be necessary to demonstrate at the sprint review session. Much easier for them to prepare for the demo.
Always talk in business language. We found a very usable simple principle.
There should be no technical term in sprint review.
Try to communicate why you developed something, what kind of pain you remove, which job, and whose job is simplified. Communicate in a language that the audience understands, they can directly imagine an impact on their life.
Keep it short and simple. Guy Kawasaki, a great speaker, and entrepreneur defines great presentation with the 10-20-30 principle. 10 slides, 20 minutes, 30 points font.
Well, in the demo you maybe do not need to have a presentation (btw, it helps a lot from real life), but 10-20-30 is applicable even in the demo:
In all cases prepare for the sprint demo part:
Keep the timing according to the agenda. Scrum Master is responsible for that. Scrum Master moderates the sprint review. The Product Owner is the leader of the meeting. She represents the team, the head of the development body. Team members demonstrate functionality.
All team members participate to some extent in the sprint review session.Product Owner+Scrum Master + Team.
All team members participate to some extent in the sprint review session.
Product Owner+Scrum Master + Team.
Our vision is to provide the tool for Scrum teams that saves time and energy with boring stuff. We saw how more than a hundred of Scrum Masters prepare for the sprint review session. We were keen to understand what kind of information they have to provide to the stakeholders. What we saw were dozens of minutes spent on the preparation itself. We are pretty sure that for those ScrumMasters this is not a way to live a life.
Therefore, we built the sprint review document directly into the tool from which it can be printed, saved to PDF and then sent to stakehodlers. All done in one minute, you do not need to work on the presentation for one hour.
With ScrumDesk you can, however, prepare far sooner before the sprint review for the sprint review.
Komplexné produkty umožňujú paradoxne jednoduchšiu a rýchlejšiu tvorbu produktov. Ak priorizujete požiadavky delené...
Počuli ste o user stories splitting? Veľké požiadavky sa majú rozdeliť na menšie. V článku nájdete viacero príkladov...
Ako správne písať požiadavky v agile? Typické chyby pri písaní user story. Product ownership zmysluplne....
Nenechajte si ujsť výber toho najlepšieho z Agile, s čím sa stretli naši mentori. Nielen zo sveta produktov, vývoja, tipov a trikov, ale občas aj humoru. Posielame pravidelne, raz za občas :) #QualityOverQuantity