YDS: What Should a Scrum Team Discuss at Sprint Review?

[@b.a9891]

I would say data trumps stakeholders at any day cause even stakeholders sometimes either have old data or assumptions as well ..

[@josepatricioochoagarza1271]

Kinda confused right here. Isn't the objetive of the event to review last sprint? Seems like looking to much into the "next thing" needs to be addressed on Sprint Planning. Am I missing something? Anyway, love the videos!

[@PrasannaMunukutla]

If I may add, Review is for inspecting and adapting. Based on the progress in current sprint, users or stakeholders can give their inputs if any changes in the backlog to be done. PO would take decision to reprioritize the product backlog based on this info. During spring planning, looking deeper and planning happens on the reprioritized list

[@Slix436]

Many thanks to you to for supporting the COP , good job, i will like to have you as my trainer for my PSM2 Quick question :there are 2 refinement during a sprint , can you break down the advantage and what sprint does it serve , current or next sprint ? Because my understanding is that the first refinement is for current and the 2nd is for next sprint , can you please make a video on this Thank you !

[@PrasannaMunukutla]

I'll take this opportunity to seek review of what I'm doing as SM, I'm coaching the discussion to be around Sprint goal. Sharing the increment value of the product from developer to stakeholders. Encouraging Developers and PO to seek feedback on the items that met Definition of Done. Guiding PO to invite end business users to review.

[@veccher]

it always bothered me because usually the prouct owners i've worked with hadn't used this meeting to it's full potention in my opinion, usually it's just the team showing what they've done to the PO, the feedback rarely goes beyond "this button should be another color", once when i was PO i called some stakeholders, briefly explained and showed what we had done in the last sprint (that they were already aware about), and asked one of them (not choosen randomly, it was related to the goal) to just show how he uses the product, he explained his entire routine (related to the product) to the team, and we learned a lot from it.

[@hugodimadrid7877]

I have a big question, literally . main topic dev manager and SM. How should I work with a dev manager if I am a scrum master? How does it fit the dev manager in scrum ? how to avoid overlap with SM deciding who does what ? is it recommended? what would be their responsibilities as dev manager? and how this position fits with every member of the scrum team(PO,SM,Development Team) example collaboration, resolving conflicts, improving, etc ?

[@aleksandraivanovic1904]

It's off the topic maybe but will ask two questions - 1. how do you approach when your architect wants to/ is leaning towards Kanban and PO wants to keep the Scrum format? The program decision was we do Scrum though. We had the capacity to add one not-pointed story into an active sprint, had developer who was keen to pick it up and was completely available, and PO didn't like the idea of bringing it in as it was not planned and we don't know how much it will take to complete also we didn't include QA to estimate as well. In my opinion, it was useful to accept this it's completely legitimate, otherwise, we will have the developer sitting and maybe waiting to help QA guys with testing plus this additional story was something that on the program level was identified as we should kick off asap. PO was annoyed architect didn't inform the team but injected it into a sprint. 2. How to approach when we have in the last 4 sprints a lot carry over work due to many reasons? What are you allowed to do? Please note we are a team in forming stage. :) Thanks! Great channel btw. Love your podcasts!!!!

[@ZacharySkaggs]

If I can ask, why does your architect want kanban, and why does your PO want sprints? What is the problem each is seeking to solve with their respective proposed solutions?

[@tomaszniemiec]

🛬 I think I already answered this one in the last video, so without repeating myself: product's current (after the addition of done work in sprint) state and its future direction (by referencing the backlogs state and shape, at least top of it), collect feedback from the attendees to both and update the backlog. 🛫 As much as I agree that data/evidence is king (Scrum is an empirical framework, right?), what I would like to emphasize is that the data analysis, collecting and reviewing happens through the sprint. On the review, we discuss the outcomes or decisions made based on them. Oh, and it is not a demo 100%.