If we demo in between sprint, won’t Product Owner change his mind again?
People usually forget the fact that Sprint Review is not for Product Owner but for the Stakeholders to review the work done by the Development team. Product Owner will get the demo of the product backlog items once it is done by the development team.
Product Owner of course will provide the feedback immediately and any changes pertaining to the feedback will be done soon. Product Owner after seeing the product backlog item in the form of a usable feature, he/she can change his mind.
It is possible that PO assumed something and is not satisfied with what is built. Also, possible that PO can change his mind on his assumption were wrong with how the product is built.
Product Owner knows the pulse of the customer and the market and decides/changes based on the same. Moreover, team should validate their assumptions faster by demoing it to the product owner as fast as they can.
What are the challenges a ScrumMaster face as they don’t have authority?
Challenges come only when you have authority. People who came from command and control background like Project Managers and line managers finds it difficult as they cannot do authoritative command anymore. Without authority we can get all things done.
Passionate and concerned conversations with more clarity on the subject can get the work done than authority and that’s what the Scrum Master need. A Scrum Master doesn’t have to face challenge without authority.
Scrum Master doesn’t own the outcome, team does. Scrum Master is there to facilitate and if team don’t listen to Scrum Master, they must fail and learn the hard way.
When you get estimate from team, how will you make sure it’s right?
Scrum Master is not responsible for the estimates, only the development team is. Scrum Master does not get the estimates from the team, they do it for themselves to complete the work. If they are wrong or have provided a different estimate, they will make sure it will be taken care as part of their retrospectives and do it right on the upcoming refinement events.
Scrum Master just must ensure that they have understood it right by facilitating the backlog refinement event. Scrum Master doesn’t conclude that the estimate is right or wrong.
For a new project, for 1st sprint, how to decide how many stories to commit for sprint?
We can take 2 probabilities here, one is considering the team is new and considering the team already worked together. Since the team is new they don’t know their velocity and so they agree as a team to pick up certain stories and work towards completing them.
If they complete them sooner, they will pick up new stories and continue working till the end of the spring. If they are unable to complete, they have learned how much can be done in the upcoming sprint and they decide accordingly.
If the team has already worked together, they know their velocity and they can pick items based on their velocity.
How do ScrumMaster influence business to understand not to push the team?
Scrum Master should understand that development team should work at a sustainable pace to deliver things happily. At the sustainable pace, business people, customers and development team will be happy. If the development team is pressurized by adding more PBIs without changing Sprint backlog, they will do it for the sake of business, once or twice.
If business continues to do it every now and then, team will be demoralized and it will be reflecting in their work in the form of less quality, half done work, more leaves and so on. If they are pushed more, they will become dysfunctional and lose focus on the sprint goal.
Scrum Master should teach the business to understand delivering at a sustainable pace and as well the data to make them understand how team delivers when they are not pushed and how they deliver when they are pushed. This will also help the business in understanding more better. Also, team’s happiness index should be collected and presented to business as well.