New answers tagged

0 votes

When should a user story be marked as "blocked" and not "To-do"

"Blocked" should never be a state in a workflow, which includes a status in a Jira workflow or a column on a board. Calling something "blocked" is a description of the work, but ...
user avatar
  • 17.2k
0 votes

When should a user story be marked as "blocked" and not "To-do"

"Blocked" is normally reserved as a state when the team as a whole cannot progress the item. So in this case, I would not consider it "blocked", because the team can do meaningful ...
user avatar
  • 7,540
0 votes

When should a user story be marked as "blocked" and not "To-do"

I'd ask the team what benefits does they find from having two user stories for the same piece of functionality? I advise teams not to split backlog items into stories for specific disciplines. In this ...
user avatar
0 votes

What are valid reasons for increasing the story points for a user story during or after a Sprint?

Story points are used to measure the overall effort required to complete a product backlog item. In my opinion, changing the story points during/after a sprint is not fair as it hinders the ...
user avatar
0 votes

Protecting the team against injection

Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan ...
user avatar
1 vote
Accepted

How should tasks be named in the Kanban approach?

I strongly believe you're mixing up concepts, so I'll take some wild guesses here. In Scrum, the tasks would be named sprints. You may mean In Scrum, the goals are defined per sprint. Where the ...
user avatar
  • 8,341
0 votes

How should tasks be named in the Kanban approach?

In Scrum tasks are not to be confused with sprints. The sprint is a timebox, the tasks are just developer todo items. In Kanban, tasks, if relevant at all, would be the names of the columns. In this ...
user avatar
  • 462
1 vote

How do you plan for Production Support in velocity-based sprint planning

Understanding Velocity How would a team plan for production support in a velocity-based sprint planning model? "Velocity" is often used in story-point based estimation processes, but is ...
user avatar
  • 47.4k
1 vote

Protecting the team against injection

Reflect the pain The Scrum Master can help by preparing sprint reports that highlight the impact of priority/context changes. For example: Midway through this sprint the team was asked to stop the ...
user avatar
1 vote

How do you plan for Production Support in velocity-based sprint planning

The best predictor of today's weather is yesterday's weather. Velocity-based sprint planning, as you call it, works like that. If the team capacity and sprint length don't change, if the team does the ...
user avatar
  • 13.6k
2 votes

How do you plan for Production Support in velocity-based sprint planning

If the production support overhead is reasonably consistent, then when using velocity you don't need to do anything at all. The amount of planned sprint work the team gets done will deduce due to the ...
user avatar
6 votes

Protecting the team against injection

The specifics depend on the nature of the changes and why they are happening, but it usually comes down to some kind of coaching. If the reason is an incoming "high priority" request from a ...
user avatar
  • 17.2k
4 votes

Protecting the team against injection

Normally, Scrum - and Agile in general - is something you want to use in a context with rapidly changing priorities. So the team shouldn't need protecting from anything, because you want to move with ...
user avatar
  • 13.6k
0 votes

Collaboration of product owner and team

Looking at this through the lens of the Scrum framework, the question isn't entirely clear. There is no "team leader/manager" role defined within Scrum. Having such a strongly-defined role ...
user avatar
  • 17.2k
1 vote

Collaboration of product owner and team

How often does the product owner and the team leader/manager typically meet for discussing the product and the vision as well as the roadmap? There is no team leader/manager role defined in the Scrum ...
user avatar
2 votes
Accepted

Can epics, features, user stories, span multiple releases or iterations?

As the question stands, it's way too broad to have a single answer. Considering this is a point of recurrent debate, I'd like to share my takes on it too. As Thomas said, the answer is context-...
user avatar
  • 8,341
2 votes

Can epics, features, user stories, span multiple releases or iterations?

It depends on how you define "feature", "epic", and "user story". The only one of these terms with anything close to an agreed upon definition, and even that isn't ...
user avatar
  • 17.2k

Top 50 recent answers are included