Skip to main content
Print

Overview of QA/QC Process Changes

Now that we’ve met with both the PM & Dev teams, we wanted to provide an overview of the changes in writing as well as when to expect these changes to go live.

WHAT:

  • FS Builder Checklist – Done during the build process by Devs
  • Design QA – Dev assigns to PM to complete once the Builder checklist is completed
  • Technical QA – PM assigns to Karina once the Design QA is complete
  • Revisions QA Checklist – Done during the revision rounds by the Devs
  • Final QA – PM assigns to Stephanie once the install is moved to Pressable

WHY:

  • Re-balance Quality vs Speed – Devs to focus on the quality of the builds/revisions and ask for extensions when needed; PMs to pad projects with extra time for this process change & manage client expectations
  • Accountability / Ownership – Devs to hold themselves accountable / be proud of the work they put out
  • Consistency – Quality across all Dev’s builds/revisions
  • Continuous Improvement – Always looking for ways to make the Build process smoother from start to finish

WHEN:

  • Compiling/addressing feedback Nov 22-23rd
  • Once feedback is complete, Stephanie and I will review and make edits if needed
  • Once complete, add to Jon’s calendar to push tasks to the Live Asana template
  • Alert PMs and Devs of exact launch date > PMs to update their current Asana projects with the new tasks
  • Long-term expectation – With time, PMs and Devs will get into the groove with their QAs and improve their own efficiency through the QA process
Table of Contents