New answers tagged

4

It is worth differentiating between what Scrum is (as defined by the Scrum Guide) and what is popularly associated with Scrum. For example, story points, stories, estimating, velocity, etc. are not a part of the Scrum Guide. The team doesn't communicate in the same way as engineers. They need a lot of time to discuss and hypothesise(i.e. its not what Scrum ...


7

Kanban, i.e. managed flow rather than timeboxed sprints, makes a lot of sense for research and discovery work for exactly the reasons you mentioned. Perhaps you could still produce the metrics and status reporting to keep your team accountable to management but the idea is to focus on prioritisation and sustainable delivery rather than estimation and ...


2

I'm still a bit junior on Scrum but I would like to point out something that I didn't find in the other replies. As much as the PO has the role to lead the product in terms on "what" is it we are going to do next to get the highest possible value, it is also true that the Scrum Team needs to develop in a way that they get to be as self managed as ...


2

This is a really good question. The first thing I would say is that all teams, even the highest performing ones, have room for improvement. The Scrum Master has the advantage of being able to focus on the team while the team members are focusing more on their work. This gives you a great opportunity to carefully study their ways of working and see if there ...


3

There are a couple of points to consider here: First, does the team want help following the Scrum framework. Granted, it can be confusing if they are calling you a Scrum Master and they don't want to follow Scrum, but it isn't uncommon. Scrum isn't the silver bullet. Also, many teams grow past Scrum - leaving behind by-the-book practices for refined ...


4

I have read this question several times and if I understand your question correctly, I don't think you fully understand the concept of Scrum, and how it's embedded in the organization. Let's start with what "IT requests SW update" means - do you mean workstations? (operating system, software) or software for servers, virtual machines? If so, ...


3

The Product Owner would be accountable, but not necessarily responsible for this work. The person playing the role of the Product Owner is accountable for managing the Product Backlog. This includes clearly expressing Product Backlog Items, ordering the Product Backlog Items, ensuring that the current state of the Product Backlog is visible and transparent ...


2

No, estimates should be done by whoever will be completing the work. The Scrum Master isn't necessarily a domain expert in all areas that the development team is working in, nor are they responsible for actually performing or completing the work. The way that I've usually seen this done is to either have the dev team discuss it and vote on it, or to have ...


Top 50 recent answers are included