Overview
At this point, the website will be shared with stakeholders so they can also see its progress and provide feedback. We will always refer to the initial design brief and keep in mind if it meets “good” in our MVP standards. If additional ideas out of scope are created at this stage, it will be decided if this is added in before go-live, or if it’s considered as a post-live iteration.
Once the website is in a good place, it will also be reviewed by the product lead, senior developer and designers, also known as a peer review.
Peer review
Peer review is when someone else on your team checks your work before it’s final.
They give feedback, suggest improvements, and help make sure everything is clear, correct, and useful.
Why it’s useful
- It helps catch mistakes early.
- It improves the quality of your work.
- It brings in fresh ideas or perspectives.
- It makes sure your work meets team standards.
- It makes sure the final result meets the goals.
Quality assurance
The quality assurance process in web development generally tests aspects like:
- Functionality: Checking each feature of the website to ensure it works properly (i.e., testing contact forms).
- Usability: Observing how easy it is for testers to perform certain tasks on the website (i.e., accessing news and events).
- UI: Testing visual elements to ensure they’re displayed properly.
- Responsiveness: Testing how the website is displayed on different screen sizes (i.e. mobile vs. desktop view).
- Broken links: Clicking on each link and button to ensure no 404 error pages are displayed and that it goes to the correct area.
- Performance: Running tests to evaluate metrics like page speed, bounce rate, error rate, etc
- Security: Scanning the website for vulnerabilities.
We use Silktide to assist us with these checks. Silktide also provides us with analytics on user views, web views, browser use and bounce rate.
Sign-off
Once the site has been reviewed by the product lead, a launch date will be agreed upon with the developers and stakeholders.