UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects
Select Git revision
  • update-gitlab-runner-tag-0.73.0-bb.3
  • update-vault-tag-0.29.1-bb.10
  • update-nexus-tag-77.1.0-bb.0
  • gitlab-runner-dynamic-network-policy-214
  • bb-2524/observability-operatorless
  • update-fortify-tag-1.1.2320154-bb.23
  • 2613-Kyverno-Reporter-IstioCore
  • istio-125
  • master default protected
  • update-fluentbit-tag-0.48.9-bb.0
  • 2548-resolve-errors-from-enabling-drift-detection-for-mattermost-not-operator-2
  • update-minio-operator-tag-7.0.1-bb.0
  • update-external-secrets-tag-0.15.0-bb.0
  • 2587-update-minimum-hardware-requirements-spreadsheet-to-include-vault
  • update-fluentbit-tag-0.48.6-bb.1
  • alloy-move-destinations
  • 2548-resolve-errors-from-enabling-drift-detection-for-mattermost-not-operator
  • Add_dynamic_network_policy
  • update-mattermost-tag-10.6.1-bb.1
  • 2608-promtail-warning
  • 2.49.0 protected
  • 2.49.0-rc.2 protected
  • 2.49.0-rc.1 protected
  • 2.49.0-rc.0 protected
  • 2.48.0 protected
  • 2.48.0-rc.4 protected
  • 2.48.0-rc.3 protected
  • 2.48.0-rc.2 protected
  • 2.48.0-rc.1 protected
  • 2.47.0 protected
  • 2.47.0-rc.2 protected
  • 2.47.0-rc.1 protected
  • 2.47.0-rc.0 protected
  • 2.46.0 protected
  • 2.46.0-rc.0 protected
  • 2.45.1 protected
  • 2.45.1-rc.0 protected
  • 2.45.0 protected
  • 2.45.0-rc.0 protected
  • 2.44.0 protected
40 results
Blame Permalink
2
SprintPlanning.md 1.86 KiB

Product Team

Responsible for building the COMMON Big Bang product.

Product Team Sprint Planning

Normal Rhythm

  • Two week sprints starting on a Tuesday
  • Continue to improve planning every week
  • All team members who have capacity to work on the PRODUCT backlog should attend the planning session

Work Breakdown

  • The Big Bang PRODUCT work will be continuously updated within GitLab by the Big Bang Product Manager, Anchors, and Anchor Shanks
  • The pre-planning activity will execute the following planning steps:
  1. Review current team objectives
  2. (Re-)prioritize work at the Epic level
  3. Assess ( ballpark ) amount of the work the team can accomplish within the next week
  • The planning activity will execute the following planning steps per planning "team":
  1. Review/update the currently OPEN and prioritized Epics provided by the pre-planning activity
  2. Decompose the Epic work into stories by writing new or updating existing stories in Jira to accomplish the Epic objectives
  3. Identify and capture any intra-story dependencies in Jira
  4. Prioritize the stories to be accomplished
  5. Add stories to the sprint backlog roughly equivalent to the team's capacity

Sprint Execution

  • Daily PRODUCT team standup - Should discuss EPIC level issues ( dependencies, issues,etc) and be less than 15 minutes
  • Daily EPIC team scrums - team members brief based on Jira Story or Task
  1. Review accomplishments in the last 24 hours
  2. Planned work in the next 24 hours
  3. Any blockers or helps required
  4. Individual Stories will be accepted
  5. Sprint retro ( bi-weekly to start on Thursday to inform Tues planning)
  6. Sprint DEMO - working software
  7. [FUTURE] Team capacity planning

Core Concepts

  • Succeed or fail as a team
  • Work pairing is highly encouraged
  • Collaboration/Communication will be key to team success
  • Look for ways to improve the PRODUCT and the process

UNCLASSIFIED - NO CUI