Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 3

Meeting Goalposts:

  • Wrap up last sprint
  • Level set individual expectations for next sprint
  • Look in the near term future (1-3 sprints) for epic transitions and/or tripping sticks

Meeting Landmines:

  • Any detailed discussions (technical, policy, or hypothetical), on backlog issues that aren't scheduled for this epic.  Much better held in separate, targeted forum.

Pre-Meeting Responsibilities:

  • Add tickets to backlog, if needed, being as detailed as possible.  These tickets will be assigned to an epic during sprint planning.
  • If your time off isn't represented below, add it.
  • Be prepared with some expectation of what the next sprint holds for you.

Sprint Planning Agenda

  •  Demos
  •  Review roadmap
  •  Assign new backlog tasks to an Epic
  •  ID any personnel outages
  •  Review open incident impact on sprint capacity
  •  Distribute sprint load
PersonOut datesWorking hours out of Sprint

points for LOE tasks (Mtgs, Training, Confs, Ops)

points available
Scott

99
Bob


18
Jim


18
Tony

164
Fraser

7/27-31

24

66
DJ


18
Joel7/25899
Alysa


18

Erik


18
Stuart/Drew


18

Joe


18
Dale7/19 -2124
12
Arthur7/31-4

18

Sean



Alisdair

9


Jira timeline
urlhttps://nso.atlassian.net/jira/software/projects/DCS/boards/29/roadmap


Quarter 4 - 2023https://nso.atlassian.net/jira/core/projects/JOS23Q4/timeline?atlOrigin=eyJpIjoiNzg2NDcwYTM2MGMzNDU5ZDhmOTJmNjFmZjBhMGU0M2IiLCJwIjoiaiJ9



View in backlog (assign parents)

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,assignee,reporter,status,parent
maximumIssues20
jqlQueryproject = DCS and Parent is EMPTY and status != "DONE" and type != Epic
serverIdb9f64e64-1a61-3bf5-b3ac-d97674e9bd1d


Open Incidents:

https://nso.atlassian.net/jira/core/projects/DATA/summary


Open Science Data Processing Issues:

https://nso.atlassian.net/jira/core/projects/SDPO/summary