You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do pre-planning after prioritization meeting.
It will allow to determinate which issue need additional information.
We need that to be able correctly determinate a scope of big tasks or reduce the number of such tasks. Ideally, after prioritization, we should not have unexpected items that are not related to our L train backlog.
Reduce the number of story points we are taking into the sprint since for the last couple of sprints
we have a set of PRs at the end of the sprint that almost-merged but we need a day or two to finalize it.
The text was updated successfully, but these errors were encountered:
Features related to Devfile
Features related to Monitoring
Tasks, Technical debts and bugs
Finalize issues started in the previous sprint.
Unplanned
Sprint Analysis
Availability
Metrics
Retrospective Comments
Do pre-planning after prioritization meeting.
It will allow to determinate which issue need additional information.
We need that to be able correctly determinate a scope of big tasks or reduce the number of such tasks. Ideally, after prioritization, we should not have unexpected items that are not related to our L train backlog.
Reduce the number of story points we are taking into the sprint since for the last couple of sprints
we have a set of PRs at the end of the sprint that almost-merged but we need a day or two to finalize it.
The text was updated successfully, but these errors were encountered: