Sunset 1

The main purpose of the Sunset graph is to monitor the team’s progress while following the project scope.

This graph allows you to visualize the project’s progress. It makes it easier for managers to understand, at a high level, the issues encountered by the team. Managers can then focus on anticipating potential budget excess or non-delivery of mandatory stories instead of focusing on the project’s content.

In addition to keeping managers informed, the Sunset graph supports the concept of self-organizing teams.

The Sunset graph, named this way by Pyxis Technologies because of its colors, is the perfect tool to bring some visibility to the following:

  • The scope of the backlog (orange), split into 3 categories: mandatory, important, and optional
  • The actual progress (blue), split into the same categories (mandatory, important, and optional)
  • The trends regarding forecast completion based on the team’s velocity
  • The changes in scope in the backlog.

How to read the graph?

With a quick look, managers can easily follow the progress of the team in light of their forecast to deliver stories based on their velocity. Before the first sprint, the team plots the number of sprints planned for the project (X-axis), the number of points to be delivered (Y-axis), and the forecasted velocity.

Optimistic trend (green line)
The optimistic trend, it’s the scenario where the team’s velocity increases; thus, completing all stories (mandatory, important, and optional).

Pessimistic trend (blue line)

The pessimistic trend, it’s the scenario where the team’s velocity decreases.

Sunset 2

Download the Sunset graph (in French).

The Sunset graph is integrated into Urban Turtle, an application platform that provides Agile project management tools for Microsoft Team Foundation Server (TFS). Used by more than 900 organizations and 19,000 users worldwide, Urban Turtle offers simple and effective tools for Agile team members that want to focus on the delivery of software solutions.
Previous post

An Agile manager opening his heart...

Next post

This mysterious box labeled “Agile”

gabriel bélanger

Gabriel holds a bachelor degree in anthropology and a certificate in journalism. He is interested in the human phenomenon in general as well as in communications. His rigour and strong writing skills contribute every day to making him a partner of choice for content creation. Having worked in various contexts, both within a large agency and on the client’s side, he has had the chance to familiarize with many facets of communication campaigns' development and dissemination. He joined the Pyxis team in 2015.

2 Comments

  1. psalvini@lgs.com'
    Paolo
    23/03/2017 at 10:22 — Reply

    Bonjour,
    est-ce qu’il est possible l’utilisation d’un sunset graph dans un contexte scrum scaled (multiples équipes scrum)
    Est-ce qu’il y a des pratiques recommandées pour bien utiliser cela ?

    • 28/03/2017 at 11:49 — Reply

      Merci pour votre question. Dans la mesure où il y a un backlog unique, l’utilisation du sunset graph devrait bien se faire. Si les sprints sont synchronisés, cela va simplifier la mesure de l’avancement en itérations, sinon il faudra adapter. La valeur du graphique dépendra du contexte de l’équipe et du cône d’incertitude généré par ses pratiques. À titre de recommandation, le plus important est de maintenir une seule priorisation et de laisser les équipes faire du flux tiré avec le carnet de produit. Si on se retrouve avec des équipes qui ne peuvent que travailler sur certains PBIs, on accroît considérablement le cône d’incertitude.

Leave a reply

Your email address will not be published. Required fields are marked *