developing the product backlog for a project that has many orders
Good morning People
Suppose that we have a project that have some parts:
1-Designing a new template for the web portal
2-Gathering & analysis the requirements of an electronic system then producing BRD & SRS then developing the system
3-Offering some HP Servers
5-tarining the users
now my questions is:
How can I make the product backlog?
should it contain all the 5 orders up?
can I deal with the 5 orders up as a Single product?
What would the Product Goal be? If there's enough complexity to justify using Scrum, expect the Product Backlog to be emergent as the team Sprints towards it.
+ 1 for starting with a Product Goal.
After the Product Goal I would also look into Story Mapping (by Jeff Patton). You can google it and learn how to do it.
the (project) as all has many outputs:
1-License for Api management
2-analysis and developing an electronic system
3-Integation with some systems
4-supply some servers
some of those outputs Doesn't depend on any other output, but they are considered as output of the project
How can I arrange Product roadmap, release plan and backlog?
thanks for care