How to make sprint planning fun
Not only are our sprint planning meetings not fun, they’re downright dreadful.
How does the product owner decide how successful a Sprint was? [closed]
Closed 10 years ago.
Should we create a story for vacation?
We have had a situation with a scrum sprint where a team member went on vacation for a few days at the beginning of the sprint. This led to us being behind the ideal trend on the burndown chart at the beginning of the sprint, although we caught up later since we knew we had slightly less resource and as a result had committed to deliver slightly less.
Is it reasonable for programmers to be sprinting the whole year round? [duplicate]
This question already has answers here: Do Scrum sprints mean to work at the fastest pace possible? (7 answers) Closed 10 years ago. It feels like it is not enough for working programmers just to “walk” 5 to 8 hours a day, and “quick walk” is not enough, but they have to “sprint”, every day, […]
Is it reasonable for programmers to be sprinting the whole year round? [duplicate]
This question already has answers here: Do Scrum sprints mean to work at the fastest pace possible? (7 answers) Closed 10 years ago. It feels like it is not enough for working programmers just to “walk” 5 to 8 hours a day, and “quick walk” is not enough, but they have to “sprint”, every day, […]
Split work item into prototype and main work item?
During grooming, we usually have work items which get approved based upon the team understanding that what needs to be done? The product owner does not discuss the details of how it will be done and stops the discussion if team tries so. This applies to all work items (new UI, new API or changes to existing UI/API). Product Owner’s reasoning is that getting into the details (both technical & functional) of how it will be done is something that needs to happen during sprint and discussing it during grooming is not correct. The effort estimation also happens based upon this discussion.
Split work item into prototype and main work item?
During grooming, we usually have work items which get approved based upon the team understanding that what needs to be done? The product owner does not discuss the details of how it will be done and stops the discussion if team tries so. This applies to all work items (new UI, new API or changes to existing UI/API). Product Owner’s reasoning is that getting into the details (both technical & functional) of how it will be done is something that needs to happen during sprint and discussing it during grooming is not correct. The effort estimation also happens based upon this discussion.
Split work item into prototype and main work item?
During grooming, we usually have work items which get approved based upon the team understanding that what needs to be done? The product owner does not discuss the details of how it will be done and stops the discussion if team tries so. This applies to all work items (new UI, new API or changes to existing UI/API). Product Owner’s reasoning is that getting into the details (both technical & functional) of how it will be done is something that needs to happen during sprint and discussing it during grooming is not correct. The effort estimation also happens based upon this discussion.
Split work item into prototype and main work item?
During grooming, we usually have work items which get approved based upon the team understanding that what needs to be done? The product owner does not discuss the details of how it will be done and stops the discussion if team tries so. This applies to all work items (new UI, new API or changes to existing UI/API). Product Owner’s reasoning is that getting into the details (both technical & functional) of how it will be done is something that needs to happen during sprint and discussing it during grooming is not correct. The effort estimation also happens based upon this discussion.
Split work item into prototype and main work item?
During grooming, we usually have work items which get approved based upon the team understanding that what needs to be done? The product owner does not discuss the details of how it will be done and stops the discussion if team tries so. This applies to all work items (new UI, new API or changes to existing UI/API). Product Owner’s reasoning is that getting into the details (both technical & functional) of how it will be done is something that needs to happen during sprint and discussing it during grooming is not correct. The effort estimation also happens based upon this discussion.