Did we recommend a Midpoint Review in the Collaboration Cycle Request ticket? If so, follow the below guidelines to get started.
Request this touchpoint when you’ve finalized your design and have a prototype or mockup ready to put in front of users. Research activities may include interviews and usability testing, where users will complete tasks to ensure your product is functional and research results are valid.
Midpoint Reviews require a 2 day lead time
Note: This should be scheduled before you begin recruiting research participants and scheduling sessions.
You may schedule a Midpoint Review in either of these formats:
Synchronous: Live, 30-minute Zoom meeting with Governance team, or
Asynchronous: No meeting is scheduled. Governance team members review your research and design artifacts on their own, and append their feedback to your request ticket
Note: If you choose an asynchronous review, but the Governance team decides your product requires a more in-depth consultation, we may change the review format to synchronous. If that happens, we will let you know ahead of time, in case you need more time to prepare
To confirm your prototype or mockup aligns with existing VA.gov patterns and standards and to ensure your product is ready for successful research activities. This may include usability testing, veteran interviews, or anything else specified in your research plan.
We recommend a synchronous meeting if this is the first time you’re introducing Platform to your product and/or iteration. However, if you want an asynchronous review, we'll provide feedback on the artifacts you provide to ensure they align with VA.gov standards.
Welcome to the Midpoint Review for _______ team for ______ initiative.
The purpose of the Midpoint Review is for the Platform Collaboration Cycle team to review your product to ensure it meets design, IA, content, QA, accessibility, and research VA.gov platform standards. If you are preparing for usability testing or research with Veterans or VA.gov users, the Midpoint Review feedback will inform you if there are any glaring standards issues that could negatively impact the results of your usability testing or user research. These are things we’ll suggest you fix before beginning your research with Veterans. The Midpoint Review feedback is intended to guide VFS teams toward building accessible, compliant, and consistent products for VA.gov. We highly recommend that you address Midpoint Review feedback before the Collaboration Cycle Staging Review. Lastly, please note that "must" feedback, if not addressed, could result in launch-blocking issues at Staging Review. By not addressing the "must" feedback, your team accepts the risk of being blocked from launch to the VA.gov platform. Please handle accordingly.
Collaboration Cycle moved to a new process beginning May 26th, 2022.
For those who started the Collaboration Cycle process after May 26th, 2022
VFS Product Manager completes Midpoint Review section of their Collaboration Cycle Request ticket.
All Collaboration Cycle Requests can be viewed on Collaboration Cycle Reviews ZenHub board
For those who started the Collaboration Cycle process prior to May 26th, 2022
VFS Product Manager submits a Midpoint Review ticket.
VFS participants (required):
OCTO-DE Product lead
OCTO-DE Design lead
Anyone from your team who significantly contributed to the artifacts
VFS participants (when applicable):
OCTO-DE product lead
Content, IA, accessibility, and QA specialists
Platform participants (when applicable):
Provide links or documents for the following:
Finalized design prototype or mockup
GitHub ticket for any relevant static content page and entry point updates for tool or feature (if applicable):
Regression test plans (if there isn't already a regression test plan for this feature in TestRailProduct):
Link to test cases/test plan in TestRail (draft OK):
Note: All artifacts listed must be provided at least 2 days before scheduled meeting/review. Please also ensure Collaboration Cycle reviewers have appropriate access to secured applications.
Platform reviewers document feedback in a GitHub ticket.