![]() The key word here is "rough": estimates will change once the team fully understands and begins work on those longer term items. Longer term items can remain a bit vague, though it's a good idea to get a rough estimate from the development team to help prioritize them. This means complete user stories have been drawn up, collaboration with design and development has been sorted out, and estimates from development have been made. Near-term items need to be fully fleshed out before they are labeled as such. Once the backlog gets larger, product owners need to group the backlog into near-term and long-term items. Regular review of the backlog is often called "backlog grooming" in agile circles(some use the term backlog refinement). Product owners should review the backlog before each iteration planning meeting to ensure prioritization is correct and feedback from the last iteration has been incorporated. Once the product backlog is built, it's important to regularly maintain it to keep pace with the program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |