Home/ Questions/Q 43875
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:33:50+00:00

We’ve been using Scrum on a few projects now with varying success and I

  • 0

We’ve been using Scrum on a few projects now with varying success and I now have a query relating to documentation.

In Scrum, you obviously have the product backlog (‘The application begins by bringing up the last document the user was working with.’) and the sprint task backlog (‘Implement forgot password screen’). However, in all the examples I have seen, these two items are fairly high level in terms of detail (being designed on fit on a post-it note).

So, where does the detail sit? Let’s say the client has some very specific requirements for a stock management screen, or has a complex API that needs to be integrated with on the back end, where is this documented, how and who captures this information? Is it seperate to the backlog but populated on a just-in-time basis or some other way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Sprint backlog

    The sprint backlog is a greatly detailed document containing information about how the team is going to implement the requirements for the upcoming sprint. Tasks are broken down into hours with no task being more than 16 hours. If a task is greater than 16 hours, it should be broken down further. Tasks on the sprint backlog are never assigned, rather tasks are signed-up for by the team members as they like.

    • 0