If product backlog should contain "high-level" requirements. Where to keep technical debt?

[Pietros]

There is a lot of controversy about that. JIRA Agile documentation says that in PB,only high-level requirements should be kept (as opposed to original SCRUM Framework which considers everything required for the project to be subject of the backlog).

I want to use JIRA Agile so I will adapt. However, if I keep only high-levle requirements in teh backlog, where should I store required technical tasks (e.g. unit test Framework development). It is work too that needs to be tracked and subsequently charged to the customer. The only solution I heard of was link to some user story..

Any better idea or pracice?

[Geert Graat]

Hi,

It is interesting to look at these two definitions in the JIRA Agile documentation:

• https://confluence.atlassian.com/display/AGILE/Product+Backlog
• https://confluence.atlassian.com/display/AGILE/Backlog

According to the definitions, both backlogs are managed using the Plan mode. The documentation on Plan mode describes how you can break down stories into subtasks. So it seems to me that the definition of the Product Backlog is actually a bit too narrow and you should disregard it, as the rest of the documentation assumes that all your stories, (sub-)task and technical debt is on the backlog.

Regards,

Geert