Recommended Software Process Steps

1. Requirements engineering 
1. Gather user stories from all stakeholders.
2. Have stakeholders describe acceptance criteria user stories.
2. Preliminary architectural design
1. Make use of paper prototypes and models.
2. Assess alternatives using nonfunctional requirements.
3. Document architecture design decisions.
3. Estimate required project resources
1. Use historic data to estimate time to complete each user story.
2. Organize the user stories into sprints.
3. Determine the number of sprints needed to complete the product.
4. Revise the time estimates as use stories are added or deleted.
4. Construct first prototype 
1. Select subset of user stories most important to stakeholders.
2. Create paper prototype as part of the design process.
3. Design a user interface prototype with inputs and outputs.
4. Engineer the algorithms needed for first prototypes.
5. Prototype with deployment in mind.
5. Evaluate prototype
1. Create test cases while prototype is being designed.
2. Test prototype using appropriate users.
3. Capture stakeholder feedback for use in revision process.
6. Go, no-go decision
1. Determine the quality of the current prototype.
2. Revise time and cost estimates for completing development.
3. Determine the risk of failing to meet stakeholder expectations.
4. Get commitment to continue development.
7. Evolve system
1. Define new prototype scope.
2. Construct new prototype.
3. Evaluate new prototype and include regression testing.
4. Assess risks associated with continuing evolution.
8. Release prototype
1. Perform acceptance testing.
2. Document defects identified.
3. Share quality risks with management.
9. Maintain software
1. Understand code before making changes.
2. Test software after making changes.
3. Document changes.
4. Communicate known defects and risks to all stakeholders.