The different views of the milestone

  • Updated on Jan 30, 2026
  • Published on Jan 21, 2026
  • 3 minute(s) read
Prev Next

Four views can be displayed from a milestone:

  • Overview section highlighting key points and features of the document or webpage. : Displays the milestone summary

  • Planning section highlighted, indicating the importance of strategic organization in projects.: Allows you to break down the milestone into secondary milestones

  • Taskboard interface displaying various tasks and their statuses for project management.: Displays the status of items in a task board

  • Checkbox indicating successful completion of tests in a user interface. : Allows you to launch a test campaign based on the stories of the release.

Milestones for car functionalities including starting, stopping, and signaling features.

Summary view

The "summary" view contains the information needed to track the progress of the milestone.

It contains the list of items that make up the milestone with their statuses, as well as metrics such as a burnup and burndown to allow you to track the progress of your milestone. They allow you to see at a glance whether everything is going well or whether there is a delay in the work in progress.

The display and calculation of these graphs is pre-configured in the default template.

The burnup shows the progress of the milestone while the burndown shows the rest to be done.

Overview of user stories and burndown charts for project management tasks.

Burnup

Burnup will allow you to follow up on the elements that have been finished. The vertical axis represents the amount of work, which is the estimated total effort. The horizontal axis represents time, based on the start and end dates defined in the milestone.

The graph displays 3 different lines:

  • Total effort: This red line represents what the team has committed to. If the line goes down, it will mean that an item has been removed from the milestone, if it goes up, it will mean that an item has been added.

  • Team effort: This green line represents completed work. When an element is finished, the line goes up. Ideally, this line should join the red one at the end of the milestone.

  • Ideal burnup : This grey line is the theoretical line. It shows what needs to be finished each day in order to be able to complete all the elements that the team has committed to.

Burnup chart showing team and total effort over time with ideal burnup line.

Burndown

The burndown will show the remaining effort. The vertical axis represents the amount of work, which is the estimated total effort. The horizontal axis represents time based on the start and end dates defined in the milestone.

The graph displays two different lines:

  • Team effort: This line represents daily work. When the remainder of an element is modified downwards, the curve goes down. Ideally, this curve should be at the bottom at the end of the milestone.

  • Ideal burndown: this is the theoretical line. It shows what needs to be finished each day in order to be able to complete all the elements that the team has committed to.

Burndown chart showing remaining effort over time with significant changes in January 2026.

Planning view

The planning view will allow you to plan the sub-milestones of the milestone you are viewing, in this case Delivery 1.

Sprints planning interface showing tasks to be planned for the first release.

In our model, the sub-milestones of releases are sprints. This allows the release to be divided into short and regular cycles, to plan precisely the elements to be carried out and to follow the progress of the team step by step.

Schedule and view a sub-milestone

Like milestone scheduling, adding a sub-milestone happens on the right side of the interface.

To add a sub-milestone that corresponds to a milestone in a release, simply click Button to add sprints in project management tool interface..

A window will open to create the information related to the sprint:

Taskboard view

The "Taskboard" view is the handy tool for managing and tracking actions. This is the tool that the team uses on a daily basis to visually advance elements and also see who is working on what.

Taskboard displaying tasks for a project with statuses: To Do, In Progress, Review, Done.

The table displays tasks categorized by status (for example: To Do, In Progress, etc.) as well as by original User Story. This makes it possible to track and manage all the tasks associated with each User Story on a daily basis.

Practical information

In some more advanced configurations, it is possible for an item to be closed automatically if all of these sub-items are closed. For example, if all tasks in a user story have a status that is considered "closed" then the status of the user story will be automatically closed.

It is also possible to:

  • Show closed items: An eye icon representing visibility or monitoring in a user interface context.  

  • Do not show closed items: Icon indicating hidden content, suggesting visibility toggle for user interface elements. Lines corresponding to closed items will be automatically hidden

  • Full-screen display of the task board: Icon representing a full-screen view option for images or content.

"Tests" view

The "Tests" view allows you to create tests for each User Story.

See the article on testing tools for more information on this.

This view is then used to create a test campaign (right) based on the test plan (left).

Overview of test plans with options to create new tests and manage campaigns.

To create a test campaign, click on the button Button to initiate the creation of a new campaign in a digital platform.

Creating a new campaign in the test plan section of a project management tool.

Related articles
© 2025 Enalean SAS