Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMS Sprint Plan 101 (1.3.24 - 1.16.24) #16596

Closed
11 of 21 tasks
BerniXiongA6 opened this issue Jan 2, 2024 · 1 comment
Closed
11 of 21 tasks

CMS Sprint Plan 101 (1.3.24 - 1.16.24) #16596

BerniXiongA6 opened this issue Jan 2, 2024 · 1 comment
Labels
CMS Team CMS Product team that manages both editor exp and devops Epic Issue type

Comments

@BerniXiongA6
Copy link

BerniXiongA6 commented Jan 2, 2024

Sprint 101 Capacity

All Eng: 32.1 pts
All UX: 9.1 pts
All Support: 0.7 pts
All CMS Team: 42 pts

Sprint 101 Goals & Priorities

SPRINT 101 GOALS

By the end of this sprint, this is what we're committing to have accomplished and delivered:

SPRINT 101 PRIORITIES - not yet finalized

These are candidates for projected sprint work. Prioritize tickets in this order: 1) Sprint goal, 2) CY23Q4 goal, 3) the rest of the tickets in this section:

D10 Runbook Deliverable (Epic #12238)

  • Product and Delivery - start runbook edits in S101, finish final draft hopefully by S102

Siteimprove (Epic #10201)

  • None at this time for CMS Team (waiting VHA DM to take action)

Datadog Monitoring Expansion (CY2023 Q4 Goal) - (Epic #11928)

  • NONE ZILCH

Alt Text Validation (CY2023 Q4 Goal) (Epic #15785)

Knowledge Base Enhancements (Epic #14069)

Collab Cycle (#14013) / CMS Governance (#14012)

  • Ask Blake (returns 1/4) if any collab/gov tickets to bring in)

CMS DesignOps (Epic #12843)

Improvements to Content Release (Epic #14016)

  • None at this time

ATO Documentation (CY2023 Q4 Goal)

Dependencies / Dependabot PRs

  • (average 4 pts taken on per Dev) - Dependabot PRs = 1 point each. Total points completed will vary by sprint. Berni to update actual numbers at end of sprint.

Help Team, Partners, Clients and Stakeholders Hit Objectives

Product / Delivery

DevOps

Drupal

General

SPRINT 101 UNPLANNED WORK (Post Sprint Planning)

These tickets have been added after Sprint Planning event. It's hard to predict what will actually come in, but we're averaging about 20-30 points of unplanned yet necessary Dev work each sprint. Please let your Delivery Manager know if you're needing to pull in a critical ticket that didn't make it to the Sprint Plan:

  • Defects and hurdles work can come in, as needed
  • Keep the Lights On work can come in, as needed

Refined and Ready (Only work on these after Goals and Priorities have been completed)

DevOps

Drupal

To Be Refined

Engineering Tickets that Need Refining

@BerniXiongA6 BerniXiongA6 added Needs refining Issue status CMS Team CMS Product team that manages both editor exp and devops Epic Issue type and removed Needs refining Issue status labels Jan 2, 2024
@BerniXiongA6
Copy link
Author

CMS team closed Sprint 101 at 117% of actual vs. capacity plan (49 closed points vs. 42 capacity points -- which includes manual calculation of dependabot PRs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops Epic Issue type
Projects
None yet
Development

No branches or pull requests

1 participant