Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,414,316
Community Members
 
Community Events
170
Community Groups

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

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?

1 answer

0 votes

Hi,

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

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events