Love this series, short and to the point! Is there any chance that you guys can upload practical examples of efficient scrum meetings? Like raw footage of the whole process of one of your past project that you are willing to share? Learning theoretical gives good knowledge but practical examples gives us deep understanding.
@Atlassian5 жыл бұрын
Thanks Abhi. This is a great idea. We don't have a video like this now, but we added it to our backlog and plan to shoot this in the future. Make sure to subscribe so you get notices of new videos. ^Lewis
@Tobstar0001112 жыл бұрын
@@Atlassian Hi, has this happened? Is a video like this availible?
@LanAnh-jl3tc3 жыл бұрын
Shouldn't it be reviewing sprint backlogs instead of product backlogs? Since we're doing a Sprint review, I think it makes more sense to do a reviewing on the Sprint backlog. Am I thinking it correctly?
Жыл бұрын
As far as the scope/content of the video is concerned this part was about "having a rough forecast". And as in SCRUM the next sprint backlog will consist of BPIs from the product backlog, the term chosen should be correct AFAIK.
@durvig3 жыл бұрын
Is the authoring (updating, and maintenance) of user stories considered part of the sprint? If so, is the product owner also in a position to demo or show the accomplishments in that regard during the review?
@megumin8467Ай бұрын
good video, live it
@megumin8467Ай бұрын
YEA BREH
@mainuddeenkhazi10729 ай бұрын
Product Owner starts the meeting with discussing what is completed and not from the sprint Backlog, not from the product backlog. Product Backlog is discussed in Sprint Planning meeting and not in the sprint review meeting. Time Stamp 1:25 @Atlassian
@StefanoGiraldi5 жыл бұрын
Thank you for your content. This is a great series about SCRUM! I wanna to report that there is some problem with subtitles. They are automatically detected in Dutch. I hope you could find this feedback useful to fix it. Bye ;-)
@Atlassian5 жыл бұрын
They should be working correctly now.
@pokemon2009MJP3 жыл бұрын
this is epic
@nextes853 жыл бұрын
I understand that all these activities have beneficial effect on the team performance and/or health. The issue I have with these is how do you quantify them. Your team spent 20% of their time on scrum ceremony this week, how does that benefit the business ?
Жыл бұрын
I can only speak from a software developer POV. This said. Look at it like this. Humans are no machines, you can try to optimize every minute developers spend working. But this will only ever result in short term benefits. In the long run productivity will go down. If you run a team on 100% capacity any problem that occurs has the potential to cause stress and other downsides for the team ( DEVs + POs, ...). By having these kind of meetings you increase the teams connection / engagement / commitment to their work, the product and other things. "how do you quantify them" if you must you can quantify it by looking at other metrics. You can look at the velocity, at how often tickets get rejected, count the "change" cards in the retrospective. Did the quality of bug tickets and user stories increase?You might even take a look at how often people quit their job over time and cause your business a brain drain. Software Development / Product Development / SCRUM / ... is no conveyor belt. Depending on the organization, DEVs might rarely get into contact with mid to upper level management. POs / Stake Holders might. So these kind of meetings give room to celebrate what you have done together with people that have done and benefit from the work. IMHO, something is wrong in a business when management doesn't do these kind of "time" quantification. But expects the teams that do the work to be optimized in a way that e.g. 8h/40h are fully accounted for and result in "production" all the time. Just my 2 cents
@veronicaolivares91504 жыл бұрын
Thank you for sharing!
@kdiggity12 жыл бұрын
Should understand the framework a bit better before providing such video, too many things were inaccurate one minute into the video.
@darrenwalker73432 жыл бұрын
the first step is to review what's been done (in the current sprint - yes) and what hasn't been done in the backlog - why would you waste time on looking at work that wasn't assigned to anyone or is low priority? Stupid to review the backlog when doing a sprint review of the current sprint.
@DGDG00000005 жыл бұрын
practical examples please... too much commercial speech there. Srcum is the best and our life will be better with scrum for everthing and blablabla bla...ok... NEXT ! Demonstration please. It is at the foot of the wall that one recognizes a good mason.