Sprint Planning Meeting by Agile Digest

Рет қаралды 138,627

Күн бұрын

Understanding Sprint Planning Meeting
Sprint Planning meeting helps set the context of the sprint by scoping the product owner goals for a sprint.
In Scrum, we have multiple time boxes called Sprints or iterations. In each Sprint bunch of functionalities in the form of stories are implemented to make incremental enhancements to the product under development. The Sprint Planning meeting is the kickoff meeting for each Sprint. This meeting helps set the context of the sprint by scoping the product owner goals for this sprint. It also prescribes the priority for the stories, based on available bandwidth/capacity to meet the goal and deliver the incremental value to the product.
---------------------------------------------------------------
Please read full article from the below link to understand it from textual and pictorial explanation.
agiledigest.co...
Facebook Page
/ agiledigest
Google Plus Page
plus.google.co...
You tube channel
/ agiledigest

Пікірлер: 123

@gobbaka 3 жыл бұрын

Thank you. No words. Presentation is much granular way.

@protagonist06 5 жыл бұрын

One by one I am watching all your videos on Scrum. I just loved the way you have explained the concepts with examples. Thnx :)

@skyboomshield 4 жыл бұрын

That's a really nice and detailed explanation of sprint planning .It beautifully captures all real time sprint planning activities and also focuses on the key deliverable.

@IyyappanRam 4 ай бұрын

Extra ordinary session 🎉🎉🎉

@Swamysurya141 3 жыл бұрын

Hello Niladri!! I love it , I am proud to have been part of your scrum team!!

@vrundapathak5315 4 жыл бұрын

Thank you for putting good enough details for people like me who want to learn about sprint planning. Helpful content in all the videos. Great job!!

@Najstar43211 4 жыл бұрын

Great videos. I am watching almost all your videos now

@chittishireen 4 жыл бұрын

very detailed , thank you for putting all the info with examples. helpful content.

@pawanjinger747 2 жыл бұрын

very nice explanation

@AgileDigest 2 жыл бұрын

Thanks and welcome

@EmpySoul 3 жыл бұрын

Thank you thank you!!!! Very very useful video!

@babatechs7570 2 жыл бұрын

The great informative video. Must watch

@sharmadeepika8285 3 жыл бұрын

Thanks for this wonderful video , really helpful

@maval10 3 жыл бұрын

Thank you in a million. Bravo!

@getnetdegfe3244 3 жыл бұрын

@naresh6480 4 жыл бұрын

Very Insightful and explanatory..Learned and got clarity on many doubts .Thanks a lot .

@AgileDigest 4 жыл бұрын

Glad to hear that

@PriyankaSingh-tw5my Жыл бұрын

Mind-blowing session

@AgileDigest Жыл бұрын

Thank you

@pavimahesh 6 жыл бұрын

GReat explanation.. really helpful Thanks a lot.

@rumanaamin6329 6 жыл бұрын

very good explanation. great job

@carlyhawken1695 4 жыл бұрын

Hello!! I really want to thank you so much for this video!! New to a B.A role and this has been fantastic in grasping the concept of 'sprints'..

@AgileDigest 4 жыл бұрын

Welcome Carly.

@Henryobazee8690 4 жыл бұрын

How is your new role? I guess you are adjusting well

@Abhishek-qy2zj 4 жыл бұрын

slides & content is very good

@rays8102 4 жыл бұрын

Great Job!

@jayashreetoradmal3255 2 жыл бұрын

Excellent explanation

@vijayoz 3 жыл бұрын

Nice video with sufficient detail in each section. Thank you. Would you have a sample excel sheet of your capacity planning please?

@gauravkesarwani585 4 жыл бұрын

Thanks Niladri, very helpful

@AgileDigest 4 жыл бұрын

My pleasure 😊

@mazda3dude1 6 жыл бұрын

Great Videos! Thanks for sharing

@AgileDigest 6 жыл бұрын

Thank you, and welcome.

@lacks123 4 жыл бұрын

Great Bro. Excellent representation. Love the graphics and explanation. Cheers

@AgileDigest 4 жыл бұрын

Much appreciated!

@JustKuldeep 5 жыл бұрын

Excellent video ! Could you share sample summary report ?

@vicramaditya9 4 жыл бұрын

Great practicality of the sprint planning. Excellent video. Could you share these excel-like Capacity planning and summery ?

@wanglijun9190 5 жыл бұрын

Thank you!

@sarangc9714 4 жыл бұрын

Hi, Very good channel. All videos are really good and detailed. Thank you for all your efforts in doing these videos. Can you please suggest any good books or ebooks too

@nitinagarwal3813 6 жыл бұрын

Great videos. I am watching almost all your videos

@AgileDigest 6 жыл бұрын

Thank You Nitin, Glad to know you like them.

@sriramr1873 5 жыл бұрын

excellent useful video thanks

@mrvinodkorrapati 5 жыл бұрын

👍Explanation is in detail....Very well done...Do JIRA has this feature of capacity planning?

@AgileDigest 5 жыл бұрын

Yes with external Plugin. Not from Default Jira.

@you1ashu 3 жыл бұрын

Good explanation ...

@ankimajain 5 жыл бұрын

very helpful

@satishkanuri 2 жыл бұрын

Is jira tool dosen't have this capacity planning things? I am new here please let me know Is it good that we fallow both jira and Alm tools? Thanks in advance

@olegkramar669 Жыл бұрын

As I know this is anti-pattern when tasks are assigned during Sprint Planning. This can be done during the sprint. That's why estimations are in story points. We don't know who will make the task

@bendeb9411 5 жыл бұрын

bro u are awesome.. how do u realistically do this in an organization?

@piyushsinha1659 5 жыл бұрын

Awesome

@mannythomas4741 5 жыл бұрын

You are an amazing teacher! Great explanation in simple language.Just 1 question..... when you talk about analysis in your team,does that mean a business analyst does that? as far as i know there is no BA in the scrum team and PO does the analysis.

@AgileDigest 5 жыл бұрын

Yes you are right, there is no BA role in Scrum as per book. The Analysis here is the technical analysis (if any) before starting the development.

@mannythomas4741 5 жыл бұрын

Agile Digest Thanks so much for your reply! so when you say as per book do you mean to say that there is a BA in the scrum team in real life? if yes how does he help the team? does he mostly work with the PO? I want to know because i work as a BA now and I do come across job descriptions that say BA WITH AGILE experience. so just wondering how do they fit in?

@AgileDigest 5 жыл бұрын

Yes I have observed that. though PO can take help from BA or story author to get story created, which sometimes Helpful to remove bottlenecks of incoming stories. but Only PO should have the accountability of all User story.

@mannythomas4741 5 жыл бұрын

Thank u so much sir!I loved all your videos.Its helping me alot at work!!!

@gaithkadir2698 4 жыл бұрын

This is one of the BEST presentations and visuals I have seen on this subject

@vidyajavisetty9260 Жыл бұрын

Thank you for detailed explanation sir. .have a query why are 2 resources estimating hours for analysis ,dev and testing?...other task resource task of code review is fine. But 2 resources estimated for same topics and thy are being counted which was bit unclear for me

@AgileDigest Жыл бұрын

This is just an example. There may be possibilities that the story needs two different technology to work on let's say java and oracle, one person with Java expertise another having oracle expertise

@vidyajavisetty9260 Жыл бұрын

Thank you sir, this clears my doubt.

@mohanparthasarathy1777 4 жыл бұрын

Excellent Presentation. What tools you use for the graphics and pictures?

@AgileDigest 4 жыл бұрын

PowerPoint and PhotoShop

@MrSivram28 4 жыл бұрын

@@AgileDigest Hello, do you have Scrum master/JIRA presentations for purchase?

@AgileDigest 4 жыл бұрын

Sorry, we dont have readymade presentation to sell.

@syedrajesh2421 5 ай бұрын

அல்லாஹு அக்பர்

@gabrielteixeira356 2 жыл бұрын

One question is: How is the emergence of meetings or casualties (like needing to go to the doctor or the like) seen in the team's capability when we talk about things we can't predict??

@SatrioBudiDharmawan 4 күн бұрын

the article no longer accessible

@jetsfromnewjersey1377 2 жыл бұрын

I am new to AGILE WORKING ON CERTIFICATION Does the sprint planning conduct in begining of each sprint or just one meeting If it does in every sprint how does it effect on sprint hours

@AgileDigest 2 жыл бұрын

Yes

@shubhrendusinha 6 жыл бұрын

Great one.. quite explanatory. One question I have - the capacity we are referring to here, is after excluding the fixed overheads like time spent for grooming, DSM, retro etc ?

@AgileDigest 6 жыл бұрын

Yes. That's correct.

@TargetUPPSC2024 2 жыл бұрын

Bought the sprint planning sheet but the price too high compare to excel standard

@AgileDigest 2 жыл бұрын

The template you have purchased in Sprint planning summary report creation. It cost you USD 8.5, kind of a cost of a coffee. If that cost is too high, we have nothing to say. you should have requested the support team to get the screenshot, in case expected something different than the video explains. it's the exact same copy explained in the video.

@mateoelizalde4555 2 жыл бұрын

In how many days is it normal to divide an 8 hours S.P. meeting (4weeks sprint)?

@prabhakarreddy3817 6 жыл бұрын

Awesome Video

@AgileDigest 6 жыл бұрын

+Prabhakar Reddy thank you.

@prabhakarreddy3817 6 жыл бұрын

Can you please share that excel sheet to my email id ?

@AgileDigest 6 жыл бұрын

+Prabhakar Reddy it's downloadable, from capacity planning article at agiledigest.com

@prabhakarreddy3817 6 жыл бұрын

I have a question, let’s assume that I am running 2 week sprint, my team size is 5, so total hours is (40*10)= 400 hrs and I am starting my sprint on Monday and sprint ends on after 10days (Friday), on Monday I have conducted sprint planning for 4hrs . My Question is- will I need to deduct that 4 hrs for every one? Or just plan for 396 hrs only ?

@AgileDigest 6 жыл бұрын

+Prabhakar Reddy for everyone, refer the Excel, it will be clear to you.

@vivekbhatt3051 3 жыл бұрын

Sprint hours 355, Unallocated hours 18 that time what to do? Can we consider next sprint tasks?

@AgileDigest 3 жыл бұрын

@MachineOverlords 4 жыл бұрын

Does anyone know of any good videos on scrum or agile?

@jaybuddhadev 4 жыл бұрын

is it advisable to estimate the effort in hours, isnt it anti-agile? and also often inaccurate as there are blockers and other kinds of surprises, hence they came up with the story points in the first place... Please advice, as being a SM i used to avoid doing micro-estimation of persons available bandwidth in a story on individual user-story

@AgileDigest 4 жыл бұрын

Its not advisable estimate your story on effort, Your story has to be estimated on Story Points, However if you are creating subtasks under story, subtask should not be estimated as story Point, You should estimate sub tasks with hours. Its perfectly ok to nit having subtask if your team is mature enough, to easy transition from Traditional way to Agile, you have have both and eventually move to only story.

@deenikas1130 4 жыл бұрын

In the video (22nd min) you say “we do story point estimation and not effort estimation”. What is the difference between the two ?

@AgileDigest 4 жыл бұрын

effort estimation we do on time, days, hours etc. Story Point estimation is for estimating the relative size. those are two different unit

@deenikas1130 4 жыл бұрын

let’s say 1 story point is equivalent to 8 hours of effort and after grooming we feel it needs 14 hours of work, so we estimate it as 2 story points rather than saying 14 hours. Is my understanding correct ?

@AgileDigest 4 жыл бұрын

No you should not estimate story points, based on effort hours.

@vrundapathak5315 4 жыл бұрын

If I may say something on this discussion, then it's that, that I think we should think of 'Story Points' as a different measuring unit in Scrum way of working. And this unit is only meant to be used to relatively understand which story card is relatively bigger or smaller than other story cards in a given scope of Product backlog or Sprint backlog. Hi Niladri, Please correct me or reword my above understanding, as needed. Hope I helped. Thanks.

@MyFraggi 4 жыл бұрын

@@deenikas1130 Story Points are just relative estimation to measure the complexity, uncertainty, risks, dependency, amount of work...its just a number to describe difficulty level of the story...while actual measure is the capacity...i.e. amount of hrs needed n a developer can give to complete the story status to be 'done'

@martintapp7153 5 жыл бұрын

Good video, but you don't normally refine and estimate in the planning meeting. This is best done using relative estimation against previous stories in a separate refinement session.

@veltmanoe 5 жыл бұрын

Your videos are very informative. Please can I get a copy of the excel capacity and report template?

@AgileDigest 5 жыл бұрын

please visit agiledigest.com, the templates are available there.

@veltmanoe 5 жыл бұрын

@@AgileDigest Thanks!

@ginisrinivasrao 4 жыл бұрын

In the product backlog/refinement video, it is being told that the product grooming should not be done before sprint planning. But in this video, it is told that product backlog grooming is a part of sprint planning and can be done before that. Kindly clarify

@AgileDigest 4 жыл бұрын

Grooming can be done separately or with in Sprint Planning, I recommend to have the grooming or backlog Refinement much before sprint Planning to optimize the The Planning Time and mature the Backlog Health and get the benefit of healthy backlog

@Vijay-xs6bx 2 жыл бұрын

Can u plz share this excel sheet

@bushrasingh6283 4 жыл бұрын

what tool the report is in?

@AgileDigest 4 жыл бұрын

Excel

@rishikeshb5171 6 жыл бұрын

can u upload videos on SAFE

@AgileDigest 6 жыл бұрын

Hi Rishikesh, we are still have scrum areas to complete, once done we will start creating and uploading video on SAFe. it may take some time. Sorry for the inconvenience

@asitp2001 5 жыл бұрын

in Sprint Planning can Other Member participant apart from Product Owner, Scrum Master and Dev Team?

@AgileDigest 5 жыл бұрын

Primarily These scrum team roles should join. Other members its not restricted, if there is a need of other member , that you think can add values to reach the objective of sprint planning then you can invite them too. for example many teams do backlog refinement during planning , where you may need to resolve cross team dependencies.

@buildingeveryday6188 5 жыл бұрын

14:36 So during a Sprint planning, we actually do grooming, what is the point of having them separated?

@AgileDigest 5 жыл бұрын

If you are having your grooming separately and in advance, that's great. It's always good to have them in advance. but if any team sont groom their stories earlier, then the use the Planning time make the story groomed. secondly during sprint review if new story came in priority which was not groomed earlier, groom that story also

@godwinnamaya913 4 жыл бұрын

Why is the task estimation in Hours instead of Story points?

@AgileDigest 4 жыл бұрын

At Subtask level we estimate the effort, not the size. One user story with a story point may have multiple subtask with effort.

@dotunokusanya 6 жыл бұрын

fantastic video, please can you show real examples

@AgileDigest 6 жыл бұрын

Thank you. Can you please explain what do you mean by real example? you can attend Agile Digest Sprint simulation classes to experience it in real.

@gsgidney 5 жыл бұрын

"Cappa-City" "Doublemint Team" Punctuation is key to communication. My apologies, it is very difficult to understand. Love the charts and the breakdown

@MrSivram28 4 жыл бұрын

You're a very ignorant person. English is not the first language of everyone. Stop being narrow minded and prejudice.

@palash09ful 5 ай бұрын

audio is very low.

@sumit-oj8ec 4 жыл бұрын

This looks too granular. I guess rather going story by story one by one where PO will describe the scope and then the technical team will create tasks and put hours. (in this there will be too much time waste for PO. they have to wait after every story so that Technical team create task and put hours against each story. Other simple approaches - SM will calculate total capacity hours for sprint say = 160 hrs. and for team 1SP(story point )=8 hours approx (it can vary team to team). so the team can commit @max = 20 SP (160/8)= Now Divide session in 2 parts. One part where the PO will explain the story and team will do just estimate the story based on SP. once they take 20 SP then PO's role is over. Second part - now the Tech team will create subtasks understory and assign hours. if in case anyone thinks that he is overloaded or underutilised we can ask PO's to move or bring any new story.

@AgileDigest 4 жыл бұрын

Correct

@rajeevsinghal6439 3 жыл бұрын

You can't compare story point with hours so saying 1 SP=8hr approx is wrong. story point is a measure of relative complexity and cannot be measured in hrs. My thought.