Search Results

What can be really helpful in this situation is to have a definition of value. For example, it could be that your definition of value includes satisfying the organisation's strategy as best as possibl …

There are two main reasons why a single Product Owner is preferable: One Voice A single Product Owner means the delivery team only has to worry about one person's opinions. They get to focus on deli …

Perhaps you could suggest an experiment? Run for 4 weeks with only the Product Owner making priority decisions and see if that makes things better or worse. If things don't get better then you can re …

Quantifying value can be a challenge. This is because: Your organisation may not have done the detailed analysis necessary to work out potential benefits, costs, etc. Value may also include non-fin …

A guiding value of agile is individuals and interactions over process and tools. What this means is that agile favours conversation and interaction between team members. This is one of the reasons th …

This is a really good question and one that doesn't get asked enough! Some things you can do to gain confidence in the feasibility of an idea: Build a business case for the idea (testing likely value …

It isn't clear from your question if you are following the Scrum framework, but if you are then the Scrum Master should be pointing out the following from the Scrum Guide: The Product Owner is the …

Sadly this is not an unusual situation. It is what I would describe as "silo thinking". I would recommend that you favour collaboration over having a clear definition of responsibility. Look for a way …

I would recommend asking the team. They will have a good idea on what kinds of structure is suitable and by being included in the decision making process will be more likely to buy-in to the chosen ap …

How can we know what profits and losses are associated with this feature? How do we know how much this feature contributes to the revenue of the whole product? This can be a challenge, but it is pos …

"Three bloody roles, Scrum has, and only three. If you can’t get that right, don’t call it Scrum, OK?" - Ron Jeffries (one of the original agile manifesto signatories). The Product Owner role is …

One of the big differences between Scrum and traditional development is the Product Owner role. The Product Owner becomes the single source of truth for the team in all matters relating to requiremen …

Waiting for the Product Owner to be away before having the conversation is not a good Scrum approach. It is better to have an open discussion as a team and resolve the problem with everyone present. …

Excellent answers already, but I will add a bit. Should we limit who can submit stories in Scrum? Anyone can propose a story is added to the backlog, but the process is typically as follows: T …

The first thing to note is that you don't have to plan everything before you start the sprint. Mike Cohn has a really good post on why teams don't need to think of everything in sprint planning. Don't …