How to use Backlog document

[aimam]

Hi everyone,

Could anyone please share instructions how to use the Backlog (AG_16) template document properly? The instruction written on the template is too vague and does not explain how to use the template.

I appreciate it. Thank you

[Sonam · Accepted solution]

Hello,
Those numbers represent the ideal person days for a particular release, say release #1. And then these ideal person days are divided into different sprints. Taking changed estimates and new requirements into consideration it will take 6 sprints to complete the project back log for release #1 ( according the the backlog template example).

Please check page number 20 and 21 from the Agile Sprint Planning accelerator to see how to calculate idea person days and the Velocity, so you can understand the burn out chart, which tell you how many ideal person days are left after each sprint.

Regards,
Sonam

[aimam · Accepted solution]

Thank you for your answer. I do have one more follow up question to anyone who can help mew. So after using it for sometimes, the backlog document is pretty good. However, it is still an excel template and I can't input a more detailed requirements with all the user configurations in there. Is there a word document template to have a more detailed Business Requirements with space for configurations and simply space to put more information/ paragraph?

Thank you for your help

[Sonam]

Hi,
The backlog document is used to collect all your delta requirements during the fit to standard workshops in the explore phase. Once you have documented all the delta requirements in the backlog template. You need to define the Priority of these backlogs whether they should be Must have, Should have, Could have, Would have. Depending on the Priority, the project manager is also responsible to set the priority rank for those backlogs. According to the ranks, the team decides in which Target Release and Target Sprint, a particular backlog needs to be completed.
To understand how to define these priorities, you can refer to the Agile Release Planning accelerator
This backlog document acts as an input to your Realize phase, where you pick each backlog from the backlog template and perform relevant activities in your weekly or bi-weekly sprint.
Attaching a screenshot of a sample backlog template for your reference.

Regards,
Sonam

[aimam]

Thank you for your answer. It's much clearer now. What about the 'Release Planning & Burndown" tab? What those numbers in the template mean? It's still confusing to me how the template trying to measure work. Thanks for your feedback

[EkD]

You have collect requirements during explore phase to perform fit-to-standard as product backlog in Cloud ALM using the AC_16 Guidelines

https://blogs.sap.com/2022/04/29/agile-project-management-with-sap-cloud-alm/

https://support.sap.com/en/alm/sap-cloud-alm.html

[aimam]

Thank you Eswar. Unfortunately, the organization I work for has decided to track these requirements manually and we won't be using any alm software. Do you know a word doc template to capture more in depth requirement to complement the backlog?