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 ...
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 ...
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 ...
2
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 ...
1
vote
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 ...
1
vote
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 ...
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 ...
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 ...
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 ...
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 ...
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 ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
agile × 1411scrum × 791
user-stories × 148
kanban × 127
team-management × 114
sprint × 111
scrum-master × 99
software-development × 92
planning × 79
estimation × 78
jira × 66
story-points × 53
product-owner × 51
project-management-style × 48
waterfall × 44
agile-coach × 41
project-team × 34
requirements × 32
methodology × 31
product-management × 30
backlog × 29
development-process × 27
communication × 26
tasks × 25
testing × 25