Skip to content

CS Sprint Management

Customer Success Sprint Management

The CS Team publishes sprint updates to inform teammates and customers stay informed about what we're working on, and invite them to engage further in topics that they are interested in.

The core sprint reporting topics:

  1. Population - Work done to influence populatio growth/ Number of residents
  2. Housing Stock - Work done to influence the housing stock in the city
  3. Product - User Guide edits; User trainings conducted; App feature requests and bugs raised

Using Gitlab for Sprint Management

The CS team uses Gitlab tickets extensively to manage its work. Tickets created for CS work will include:

  1. Milestone: The group milestone such as "Group Sprint xx mm-dd - mm-dd" will be used for all tickets. Where the delivery date is unknown the CS will default to the next available milestone. Where the work detailed in the ticket is likely to run longer than the sprint cycle, the CS team member will endeavour to create tickets in "sprint-size" chunks.

  2. Label "cs-ops": This will be used for all tickets created by CS team.

  3. Labels "housing stock"/"population"/"product adoption": These will be used where the ticket details fall into one of these categories

  4. The Head of CS will use the Handbook User Board: CS Sprint Milestones that will have the label "cs-ops" and the respective milestone for planning and tracking sprint progress.

Sprint Reviews

Sprint Planning and Retrospective Review is done every 2nd Monday during the Customer Success Team sync.

Sprint Retrospective topics include:

  1. What was achieved in the previous sprint?
  2. What will move to the next sprint or will progress over several sprints?
  3. Lessons Learned/ what could be done better

Sprint Planning topics include:

  1. What is planned for the upcoming sprint?
  2. Help required within the sprint

Documenting the Sprint Update

Slides for the updates are available through GDrive as "CSM Sprint Update"

Each topic mentioned in sprint updates will be linked to a corresponding issue in GitLab. This has a few purposes:

  1. Depth of information. We provide summaries in video talking points, but the link provides a reference where the audience can learn more.
  2. Engagement. We encourage participation and the link provides an easy entry point for teammates to provide input or help on specific issues that interest them.
  3. Communication consistency. This helps us ensure that we're utilizing GitLab for all our processes and leveraging handbook-first evolution.

The sprint update recording is uploaded to DoubleGDP's YouTube channel. The video should be added to the sprints playlist: "Progress Updates yyyy-mm-dd".