Hi, good video. I would just comment on a few "non pure agile" points you mentioned, which I think are perfectly aligned with agile and more precisely scrum. - Epics - scrum doesn't say anything about stories, epics or tickets per se. It mentions items, and purposely leaves it vague. Most agile SW dev process in the world will probably try to build something that will take more than one sprint to get to the point of stopping further development. As such, it is obvious stories are tied together. Epics (or features in AZ devops) are just a context. Context is information. Information is good. Completely agile and scrum supported, as long as you don't misuse it like setting in stone a scope (stories inside) of epic, or track actual vs planned. - assigning stories to developers - scrum guide again doesn't say anything about such a thing, but it does mention that sprint backlog is items+plan. Plan is who and when does something --> assignment is completely fine for pure scrum, as long as you don't do it prior to sprint planning. If your point is that story shouldnt be assigned, but subtask should, again, scrum guide doesn't say anything about stories, tasks, subtasks. Just a plan, and you do a plan in a way best fitting your situation.
Totally agree. Orphaned stories suggest unstructured work. Epics help to understand purpose. Dependencies between tasks are also almost always present in coding and worth capturing for planning a sprint. It's a shame people push back on these obvious realities of real projects.
Also, I agree that assigning some sprint work is necessary. You can leave some open to grab in real time, but teams always have some specialists in my experience too.
How do you deal with situations where some people have a higher capacity and others have a significantly lower capacity. How does that impact the team? This was amazing. Going to watch the rest of your videos. Very helpful and practical for a starting scrum master.
As long as the capacity of each user is known before you plan the sprint, you should be fine. When things go wrong is when you expect everyone to life the same, but then realize the can't.
do you teach azure devOps for scrum master?? also as you are jira expert can you help me understand - i just certified as a scrum master, want to get some hands on as a scrum master, is jira that is practised everywhere or do i need to know more tools and do you or can you train me and what are your charges?? thanks
I don't currently teach ADO. . . but plan to do so in 2023. I would learn Jira as the skills on how to plan sprints and use the boards will pretty much be the same in whatever agile tool you use.
If you assign stories to different members, you are maximizing work in progress, increasing lead times, reducing quality, reducing collaboration, and creating silos. You know how to use the tool, but have completely missed whole point of Agile.
To get more resources and get in contact with me check out this link linktr.ee/apetech
great video
I like to watch the info with practise using
it is most useful videos
thank you
I agree 100% about assigning stories to people; accountability says it all. Thanks very much. Kate H.
Pure agilists don't like it. . .but I find that when there's $$ on the line, having accountability is needed.
I loved this video as I recently joined an org with my first ever senior role as a QA Lead. Great suggestions!
Glad it was helpful!
Hi, good video. I would just comment on a few "non pure agile" points you mentioned, which I think are perfectly aligned with agile and more precisely scrum.
- Epics - scrum doesn't say anything about stories, epics or tickets per se. It mentions items, and purposely leaves it vague. Most agile SW dev process in the world will probably try to build something that will take more than one sprint to get to the point of stopping further development. As such, it is obvious stories are tied together. Epics (or features in AZ devops) are just a context. Context is information. Information is good. Completely agile and scrum supported, as long as you don't misuse it like setting in stone a scope (stories inside) of epic, or track actual vs planned.
- assigning stories to developers - scrum guide again doesn't say anything about such a thing, but it does mention that sprint backlog is items+plan. Plan is who and when does something --> assignment is completely fine for pure scrum, as long as you don't do it prior to sprint planning. If your point is that story shouldnt be assigned, but subtask should, again, scrum guide doesn't say anything about stories, tasks, subtasks. Just a plan, and you do a plan in a way best fitting your situation.
I love this explanation!
Totally agree. Orphaned stories suggest unstructured work. Epics help to understand purpose. Dependencies between tasks are also almost always present in coding and worth capturing for planning a sprint. It's a shame people push back on these obvious realities of real projects.
Also, I agree that assigning some sprint work is necessary. You can leave some open to grab in real time, but teams always have some specialists in my experience too.
How do you deal with situations where some people have a higher capacity and others have a significantly lower capacity. How does that impact the team? This was amazing. Going to watch the rest of your videos. Very helpful and practical for a starting scrum master.
As long as the capacity of each user is known before you plan the sprint, you should be fine. When things go wrong is when you expect everyone to life the same, but then realize the can't.
Great video. Thanks. One question, who populate the epic and stories? Scrum Master or Product Owner?
It's supposed to be the product owner.
how do you show the performance of the team in a graph view
I would look at the burndown chart for this information.
Another great video! You mentioned that you were going to make videos about velocity/capacity and estimation. Are they out yet? Thanks!
Not yet. Working through my backlog of videos. . . but soon . . hopefully!
do you teach azure devOps for scrum master?? also as you are jira expert can you help me understand - i just certified as a scrum master, want to get some hands on as a scrum master, is jira that is practised everywhere or do i need to know more tools and do you or can you train me and what are your charges?? thanks
I don't currently teach ADO. . . but plan to do so in 2023. I would learn Jira as the skills on how to plan sprints and use the boards will pretty much be the same in whatever agile tool you use.
@@ApetechTechTutorials do you provide hands on training for someone who is psm1 certified and looking for a scrum master job, no prior IT experience.
@@anahash3221 Sure, check out my Upwork profile: www.upwork.com/freelancers/~01d55ed1a24784cd93
If you assign stories to different members, you are maximizing work in progress, increasing lead times, reducing quality, reducing collaboration, and creating silos. You know how to use the tool, but have completely missed whole point of Agile.
what you say about accountability sounds about right