he Product Planning process is a pre-cursor to any development activity. Depending on the scope of the problem and solution this process can take from one to five days of effort. This typically involves all of the members of the team, but can be limited to the Product Owner, Scrum Master, and Team Members who specialize in Business Analysis and Architecture.
The Product Planning process is a pre-cursor to any development and produces the following outcomes and artifacts:
Understanding and documenting the business problem and processes
Problems/limitations of the current solution or process.
A vision for the end state
Developing an initial Product Backlog consisting of User Stories that detail the functionality required by each type of user based on role
If possible each User Story should be assigned a Business Value to help determine the priority for the follow-on Sprint Planning
Each user story should have clear acceptance criteria that will drive both developer testing and our software testing service