1. Product Ideas
In this first step of the phase, the team (including scrum masters and product owners) will gather together to brainstorm ideas.
2. User Stories
After gathering product ideas, the team will work together to create user stories for each product. User stories are an informal, natural language description of one or more features of a software system. User stories are typically written from the perspective of an end user or the developer.
3. Conditions of Satisfaction
For each user story, there will typically be multiple conditions of satisfactions which are conditions that must be met for the user story to be completed. (Sometimes this step will be skipped because the conditions of satisfaction are similar to the tasks.)
4. Tasks
These are the assignments that are given to developers to be done. These are created by taking the conditions of satisfaction and writing them as tasks that will be completed by devs to accomplish the corresponding user stories.
5. Task Efforts
Each task requires a certain amount of effort. For this program, we will be using story points (in Trello). The task effort point system we will be using is how many work hours, a certain task will need to be completed. The point options we will have are 1, 2, 8, 16, 32, 40, and 80, each corresponding to a number of work hours. Note: Our program has 8 hour work days.
6. Product Development Choice
After going through these steps, the final step of the planning phase is to review all the product ideas and see which ones can be completed during the program time. We want to pick a project that we can complete within the time frame of the program.