YDS: How Does a Scrum Team Handle Scope Creep?

[@g-ronnmendoza]

Can we talk about Scope creep for Release Planning? How do we handle it if we already have a date to deal with?

[@monikaperyt831]

Hi! I am interested in your opinion about starting a career as a Scrum Master. It is pretty obvious that it's a self-reliant position that demanded courage and professionalism. But if you do not have any experience in Project Management or in programming - how to start? I am a Master in Project Management and a believer in the Agile approach. Any tips from you on how to position yourself at the beginning? Thank you in advance and best regards! Love your work!

[@AgileforHumans]

Does this video help? kzbin.info/www/bejne/gF7WaoWCedGXqrs

[@jayvut]

Can you please make a video on the relation between story points and hours? Thank you so much!

[@AgileforHumans]

There is no relation :)

[@DerekMahlitz]

@@AgileforHumans Hulk Smash there

[@PankajDhande]

Work can always be added or removed from sprint backlog until it does not impact sprint goal, so in such cases should the team keep updating estimations/story points for the sprint backlog items? If yes then such changing velocity could be unreliable when we consider it as input for next sprint planning. Please help on this situation.

[@AgileforHumans]

Velocity != Reliable to being with. It's one of several inputs we can consider in Sprint Planning. Scrum is about adding value to the product not "getting credit for points". A lot of these debates are the reasons why we no longer use the practice of points and velocity. We're hoping that our "Fixing Your Kanban" channel will, eventually as we post more videos, provide you with enough information that you have an alternative. (kzbin.info/aero/PL9uyGDiy_ChVfUxjc5gowNg0wW0gLFnx6)

[@kensaiyeahyeah123]

Question: Is testning mandatory in the definition of done?

[@FerdyGriffioen]

Depends on what the team states it is. If you don't test your work.. is the story done or not? (personally I would state that not testing is a risk you don't want to take (finding issues/bugs on a Test environment is cheaper to fix then finding it on production))

[@derekwright3631]

Great Podcast Guys

[@throwaway9383]

We have a product owner who micromanages the development team. One of the ways they do this is that they come to the scrum meeting and ask about work (even asking why work cannot be delivered early) and sometimes will pull stories that have not even been reviewed by the team into a current sprint and assigns them directly to a developer they are friends with outside of work. How involved should the product owner be in a daily scrum? How involved should a product owner be in the daily activities of the development team?

[@throwaway9383]

As I was thinking about this, I think this is a two part question. The role of the product owner in the daily scrum and their level of daily task managementu is one. The second is how personal relationships or the comfort in working with certain people sometimes lead to skipping important aspects of the scrum process and how that could be mitigated.

[@jocoign]

@@throwaway9383 The PO is not a task manager or a people manager, he does product management. He has no role in the daily scrum, the daily scrum is for the developpers so they can build a plan for the next 24h toward the sprint goal. The item in the sprint backlog is owned by the developpers as a whole, a single member of the developpers doesn't own a specific item. If this happen it will detoriate the collaboration, the essence of a Team. No collaboration = no team, just a sum of people coordinating in achieving something and the coordination is a source of waste. The Scrum team is composed of professional and they are working together to achieve what should be done to delight the customer. Avoid clan forming inside the team, as the whole team is responsible to deliver increment of working software of value that is usefull. For the analogy on a football field if the team subdivise itself, and the ball doesn't pass to all team player... you are pretty sure to lose the game which is the goal.

[@yulakis4372]

here is the situation: landscape consultant previously highlighted to the developers and recorded in the minute meetings that they do aquatic plantings for the bioswale (vegetated, shallow, landscaped depressions designed to capture, treat, and infiltrate stormwater runoff as it moves downstream). the aquatic plant for bioswale has been captured in the contract bq and the detail drawing has been signed off clearly labeled the landscape contractor will do the aquatic plants and the gabion wall which is the infrastructure labeled refer to engr's detail(others). however, the civil and structure consultant (cns) reported later to the developer that it is not under their scope to do gabion berm construction and not captured in their bq but it is an infrastructure involving sumps, piping, drainage, silt trash etc. anything that needed to solve the water pollution which landscape consultant are not specialized and familiar. developer seeking design advice from landscape consultant on the berm construction. but then cns capable to give advice on the matter. landscape keeps silent since not knowing how to do the berm. the outcome: cns advises landscape to do the berm construction and the developer needs to allow additional cost (variation order) to landscape to do out of scope (not specialized work). my experience with the developer: their management does not allow any additional cost incurred. thus resulting value engineering (VE) workout later which is never happened in our practice or experience to do VE during construction phase. VE usually be done before contract award. any advise scrum master? thank you . love from malaysia

[@vikramkanse2138]

If a developer is forced to take more work, how will a Scrum Master help the developer/team? Would Scrum Master intervene pro-actively? or will wait for developer to reach out?

[@abhishekdixit8581]

Great episode! 👍🏼 Sprint Goal is a single objective for a Sprint and is a commitment by the Developers. Q. What is the difference between forecasting and committing while doing the Sprint Planning? What will happen if we interchange these terms?

[@throwaway9383]

Enjoying the videos and here's another one. Let's say in a sprint the team plans to pull in 200 points of stories. I've heard you say that scrum is a "pull" system and not a push "system", which I'm 100% on board with, but what happens in a developer just doesn't pull very hard? IE, most devs will do 50 points or so in the sprint but one specific dev will do 5 to 10 in the same sprint. Is that addressed with the individual by management, the scrum master, the product owner, dev team etc?

[@AgileforHumans]

Why are we worried how many points an individual developer completes? Shouldn't the entire group of developers be working together on PBIs that they pulled into a Sprint during Sprint Planning?

[@haricharan6675]

Hi, I’ve a Question: “There are 9 user stories. Time required & priority levels are same, the only difference is their complexity. Out of 9, 3 are low complex, 3 are medium complex, and the other 3 are high complex user stories. How will u start the sprint and which 3 user stories will you pick for each sprint ? I really appreciate your response !

[@AgileforHumans]

Pick the highest ordered one and work on that :) That's the problem with priority is multiple things can have the same priority. The Product Owner orders the Product Backlog for this very reason.

[@opmdevil]

Yeah - I guess when you take a look at this from a beginning or disfunctional team's perspective, it looks completely different. I've seen sprints where the whole sprint was ended with unfinishes work and comptele mess because ticket scope was increasing while developers did their jobs. So, the problem was that devs wanted to be more effective so they kept on adding scope to the tickets (even there were tickets in the backlog to do stuff later) and this didn't really come up in any of the dailies. There was no forcing of work and the team worked entirely based on pull-system a and they managed to mangle couple of sprints comptely until the message went through.

[@AgileforHumans]

Why were the devs increasing scope? Didn't they realize during the Daily Scrum that their Sprint Goal was in jeopardy? Glad you found a way to help them. These situations can be difficult to solve.

[@opmdevil]

@@AgileforHumans Why increase scope and give the impression of being busy? Performance dialongs and goals set there. There is a difference when scrum master says things and the managers say the other. "The more busy you are, the more you get credit and the more you get credit, the more you get in the next compensation round..."