27

It sounds like you have team members from high power distance cultures. People may not speak up when the boss is in the room because their values require them to listen and follow, not to advise or lead. You may even notice it happening between junior and senior team members or between yourself and team members. Read more about power distance here: https://...


26

It's impossible to answer your question because "Scrum Master" and "Product Owner" are roles, not job titles. Their job positions may be different and depend on the company. For example, a Product Owner could be: A business analyst at your company. A person from the customer side (i.e. outside your company). Or even the СЕО of your company (it's not rare ...


25

I don't think there is a simple answer to this question. Instead, I think there are a number of different scenarios: A team is very experienced in Scrum and rotates the Scrum Master role. They have no need for a full-time Scrum Master. A team is very experienced in Scrum, but they still face impediments and they prefer not to be distracted, so they ...


24

The situation you describe is Scrum Zombie, not Scrum. My answer will try to organize a few of the aspects you mentioned. Software developers are not resources business needs the resource and cannot afford to lose time One of the perpetual problem of our industry is to simply assume that people are interchangeable cogs in the machine. In the situation you ...


24

According to Mike Cohn It’s quite common for a team to have a bit of unfinished work at the end of an agile sprint or iteration. Ideally, a team would finish every item on its sprint backlog every sprint. But, for a variety of reasons, that isn’t always the case. Accordingly to Scrum.org: The Scrum Goal is the creation of productive and creative ...


23

There isn't much of difference in recognition/acceptability of both certifications. One big difference is that to get Scrum.org Professional Scrum Master I you don't have to go to the training. They offer trainings, but they're optional. You only need to pass online exam and you can even try out your knowledge for free in online assessment. Despite ...


22

Product Owners Are Silent Observers in Daily Stand-Ups In the quoted description, the word participate has the connotation of "taking an active part." The Product Owner should attend, but should not participate. The daily stand-up is intended as a synchronization and coordination meeting, not a status meeting, and the Product Owner has no active role to ...


19

If you do development work in the sprint, you should estimate. If you don't, then it's better you skip on providing your own story points estimates. You can help your team with information and advice, and support them to reach consensus, but you should let the people that do the work perform the estimates, otherwise you might be influencing them in one ...


18

Story Points Estimation and Hours Estimation have different purposes. We use Story Points during Product Backlog Refinement. Story Points are good for high-level planning. When we make an estimation in Story Points we talk about the productivity of the whole team. During high-level planning, only the productivity of the whole team is what matters. Story ...


16

Well first thing is to remember that a retrospective, like a user story, is an invitation to a conversation. I wasn't there, so I can only take a guess as the meeting. It sounds like the retrospective may have ended up more focused on solution and not what the actual problem is. The scrum master (CSM is a certification, not a role) should start with some ...


16

Scrum Exposes Technical Debt Through Forecasts & Estimates As a general rule, technical debt increases the cost of future work on the product. So, even if you don't explicitly keep track of the debt, it will typically show as a drag on metrics such as the team's velocity over time. Technical debt will probably also impact your team's estimates of ...


15

Analysis There is a chilling effect when he is here. Am I overreacting? Should I just try to build up the confidence of the team? or should I ban my boss from the retrospective? In my experience, this is a classic case of missing the forest for the trees, and mistaking process problems for interpersonal ones. Let's enumerate some of the issues that ...


14

In order to make the burndown chart useful to the Product Owner (or the customer or the user or another stakeholder), then burning down based on stories is going to be the better option. Since a story is supposed to represent something that is useful and meaningful to the stakeholder, so knowing how many have been completed with respect to your definition of ...


14

Sprint In the Scrum Framework all activities needed for the implementation of entries from the Scrum Product Backlog are performed within Sprints (also called 'Iterations'). Sprints are always short: normally about 2-4 weeks. Each Sprint follows a defined process as shown below: The heart of Scrum is a Sprint, a time-box of two weeks or one month during ...


14

Am I missing something? I think you are missing the main point of "impediment", that is a blocker that the team is not equipped to handle themselves. The Scrum Master is not supposed to be a better developer than the developers or a better architect than the architect. The Scrum Master's job is to make sure the architecture decision is made. By lobbying ...


14

The key to team improvement is good retrospectives. When I started running retrospectives, I found they often just degenerated into whingeing sessions that didn't achieve much, other than giving the team an opportunity to vent our frustrations. Now I go into the retrospective with a clear goal, stated at the beginning of each one: We're here to find ...


14

There is no canonical answer to this question, although as a rule of thumb, it would be better for the PO to be from the client side, not the contractor side. The Scrum Guide says this about the PO role: The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: Clearly expressing Product Backlog ...


14

And I'm going to take the middle ground between Bogdan and Thomas... Whichever side has the more competent PO. Bogdan already listed the responsibilities of a PO. To (over)simplify it in a single sentence, however, it would be: The purpose of the PO is to act as a link between the customers and the Development Team. As such, the PO is really the only role ...


13

Summary This previous PMSE answer clearly summarizes why there is an inherent conflict in having a Development Team Member perform double-duty as Scrum Master: The Scrum Master role is a process referee role. This is inherently a conflict of interest with the Team Member role. For the same reason that you have (theoretically) impartial referees in ...


13

Hard problem; I've seen that as well in the past. Analyze deeply what it is they're trying to improve in the whole. Then ask them hard questions, trying to get to the deeper problems before jumping to solutions. why you'd need Project Management meetings how the Scrum Meetings are not supporting that How creating a Gantt chart differs from creating a plan ...


13

TLDR: Beware the 100% utilization fallacy. I'm going to ignore your stated question ('is this normal?') and instead attempt to answer the underlying question. Swarming is possible As per the Scrum Guide: Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. As a corollary to this, ...


13

The Scrum Guide does not talk about prioritizing the Product Backlog. Instead, it talks about ordering the Product Backlog. Priority is only one factor that can be used to determine the ordering of the Product Backlog. Dependencies between work items is another factor, but the Product Owner can choose any factors that are appropriate to help maximize the ...


12

Roles and Responsibilities for Team Composition This is an interesting question, because it addresses some of the subtleties of self-organization with agile frameworks. In particular, it highlights the differences between authority and influence. Scrum Team Members are responsible for identifying impediments (e.g. the team doesn't have sufficient expertise ...


12

Neither PO nor Scrum Master is responsible, but the team is supposed to conduct daily standups. As a Scrum Master its your job to facilitate the team and make sure that process is being followed. Coach them to make the standups effective as opposed to having just mechanical updates during the daily ritual. The Scrum Master ensures that the Development ...


12

TL;DR You are taking a potential team composition problem and making it your problem. That is not agile; that is a misunderstanding of your role. From an agile coaching perspective, teams need to be guided into assessing and resolving their own bottlenecks, whether it involves technical or human resource issues. Analysis I am at odds as I presume this ...


12

Is it the responsibility of the Scrum master to intervene and interrupt a team member when he/she starts telling about points beyond those 3 that I mentioned? Technically speaking, no. The purpose of the Daily Scrum is to facilitate coordination between the the Team. It's not for the Team to call off those three points by rote. Many Teams don't use the '...


11

TL;DR The Product Owner must be educated on how release planning works in an iterative development model. Fixed-scope Sprint Planning is emphatically not how release planning works within the Scrum framework. In Scrum, release planning is based on estimating the number of time-boxes that are estimated to provide sufficient time to deliver the features ...


11

Scrum says nothing about hierachy. Thr Scrum Master position is not a higher position than the PO or the DevTeam position. The idea is to not think in hierachy levels! Think about a team of peoply wanting to deliver high quality products! There is no reporting inside thr Scrum Team. It's just not needed to report, because of the high transparency ...


11

How to roll out pairing in a Scrum team? I am afraid there is no right answer to this. It all depends on the existing team dynamics. Nevertheless, what is almost always relevant is to understand whether pair programming is something your team will benefit from? If you have good reasons for it, discuss them with your team during the retrospective meeting and ...


11

Great question! A lot of Scrum Masters get boxed into Scrum Facilitators early on because that's what a team learning Scrum largely needs. However, as the team gets better at organizing itself, the facilitation aspects of a Scrum Master are needed less and less, as you are discovering. At this point, the coaching side of a Scrum Master starts to grow. In ...


Only top voted, non community-wiki answers of a minimum length are eligible