Review Process
In the Capstone Phase, the Review Process is essential to make sure projects maintain good quality. Each feature undergoes the outlined review process below and is then moved to the corresponding column on the GitHub Project Board.
User Stories Review
This step contains a thorough review of user stories to confirm they are comprehensive and accurately reflect user needs. Each story should present a clear value proposition, wireframe as description, acceptance criteria, and associated developer tasks.
As a reviewer, please respond to the Slack message as follows
| Reviewing | Review Approved | Changes requested |
|---|---|---|
| 👀 | ✅ | ✔️ |
Code Reviews
In this phase, team members go through the written code. The goal is to catch any potential errors, ensure that coding standards are met, and promote best practices for consistency and maintainability.
As a reviewer, please respond to the Slack message as follows
| Reviewing | Review Approved | Changes requested |
|---|---|---|
| 👀 | ✅ | ✔️ |
Note: Not sure what to look for in a Code Review? See our Code Review Guide.
Quality Assurance (QA)
This is where the App matches all user acceptance criterias to ensure its intended purpose and user needs. Feedback from this stage helps identify and rectify any issues before the final product release.
As a reviewer, please respond to the Slack message as follows
| Reviewing | Review Approved | Changes requested |
|---|---|---|
| 👀 | ✅ | ✔️ |