Sprints and Backlogs

Two additional options to consider for a Backlog:

• Drupal 9 https://www.drupal.org/project/burndown →
• Drupal 10 https://www.drupal.org/project/content_planner →

Both modules above support Agile Kanban board. Using drag and drop.

The first column of a Kanban board is one option to create a Backlog. This column is often titled New. But can be renamed by the user to Backlog.

Optimally, adding Swimlines to a Kanban board could allow multiples simultaneous Backlog. In addition, Kanban Swimlines could be used as Springs.

Visual examples of Swimlines at https://kanbanize.com/kanban-resources/kanban-software/kanban-swimlanes

https://archive.ph/8rBdc

For adding Agile Sprints and Backlogs in Drupal PM (Project Management), my vote goes to adding support for Burndown → in PM. Three benefits with Burndown:

• Burndown already has built-in Swimlines. Screenshot 1 → . Screenshot 2 → . Documentation → . Those Swimline which can be used as Sprints or Backlogs. Details about this in my other comment #13 ✨ Sprints and Backlogs Postponed above.
• Join efforts. Because jeremylichtman, the maintainer of Burndown, suggested it for PM. In his comment #16 📌 Port PM to Drupal 10 Active . Both pm and burndown modules could remain fully independent. While at the same time, jeremylichtman might be interested to facilitate the integration of burndown into pm. I suggest asking him.
• Dedicated module. According to jeremylichtman, Burndown module is presently focusing its efforts on a Kanban board. So it might be easier for PM to support Burndown. In comparison, content_planner → module is not focussed on a Kanban board. So it might be more challenge for pm to both support Content Planner.

This API approach 📌 Port PM to Drupal 10 Active also seems like a good idea. That I know of, Burndown does not presently have an API. But, in the future, jeremylichtman might be interested in adding this API feature to his Burndown module? In turn, PM and Burndown would be able to interact. Another benefit with an API approach is that PM could use various modules or external apps for a Kanban board. In other words, the end user could pick and choose a Kanban board to their liking. So more flexible and more durable. Because if somehow one Kanban board product is no longer available, the others would still be available.

For easier search, and communication, clarified and simplified the ticket title

@francewhoa,

Thanks for cleaning up and organising. Much appreciated.

Burndown already has built-in Swimlines. Screenshot 1. Screenshot 2. Documentation. Those Swimline which can be used as Sprints or Backlogs. Details about this in my other comment #13 above.

Join efforts. Because jeremylichtman, the maintainer of Burndown, suggested it for PM. In his comment #16. Both pm and burndown modules could remain fully independent. While at the same time, jeremylichtman might be interested to facilitate the integration of burndown into pm. I suggest asking him.

I had a brief look at the code and api in burndown. It has been written with "extensibility" in mind. Thus it is possible to "extend" the modules functionality as there is a well defined event system and proper triggers. Its not obvious for me, how I could re-use only parts of the project though.

Dedicated module. According to jeremylichtman, Burndown module is presently focusing its efforts on a Kanban board. So it might be easier for PM to support Burndown. In comparison, content_planner module is not focussed on a Kanban board. So it might be more challenge for pm to both support Content Planner.

Is this about creating a dedicated module that can be used by both PM and Burndown? Sounds like a plausible idea to me.

Just to clarify, the by "API Approach", I was thinking in the lines of being able to use PM in a Decoupled App via JSON:API.