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
The percentages below reflect the amount of capacity the team members have to work towards sprint goals and priorities. Therefore, the sprint plan commitments should be reduced using these percentages. Note: includes time off, non-sprint commitments, and new team member ramp-up.
All Eng: 48.1%
All UX: 68.6%
All Team: 51%
Are there any tickets that will carry over from previous sprint?
What do we want to have accomplished by the end of this sprint?
Determine next steps on Data Visibility Work
Top Priority (work on these first)
Reduce capacity to workshop the next product facing project we will take on for the portfolio
After Sprint Planning, we realized that we will be working with a smaller team in the upcoming Sprint since Mason and Erik will be off. Additionally, we have Paul starting with us. As a result, you'll notice a section in this Sprint Epic titled "If we have more capacity." The tickets in this section are listed in priority order and can be pulled as capacity allows.
National Park
Capacity:
The percentages below reflect the amount of capacity the team members have to work towards sprint goals and priorities. Therefore, the sprint plan commitments should be reduced using these percentages. Note: includes time off, non-sprint commitments, and new team member ramp-up.
Are there any tickets that will carry over from previous sprint?
Sprint Goal:
What do we want to have accomplished by the end of this sprint?
Top Priority (work on these first)
Reduce capacity to workshop the next product facing project we will take on for the portfolio
Help our partners and VA Stakeholders
Mature Platform
Improve Deployment
Who is On Call?
Data Visibility
If we have time
The text was updated successfully, but these errors were encountered: