| Engineering | Reduce [technical debt](https://github.com/GSA/notifications-api/issues/361) and stabilize application; carry out rigorous [testing](https://github.com/GSA/notifications-api/issues/312) of features and [infrastructure](https://github.com/GSA/notifications-api/issues/87); solve known [bugs](https://github.com/GSA/notifications-api/issues/360) | Increase app reliability prior to first partner use |
| UX | Continue [user testing interviews](https://github.com/GSA/notifications-admin/issues/592) and feedback; Kick off internal message recipient [opt-out test](https://github.com/GSA/notifications-admin/issues/395) | Gain feedback on usability and functionality in order to find bugs, streamline confusing flows, and adjust processes |
| Security | (Assessment has begun!) Respond to any assessment questions and/or needs | Keep the LATO award timeline as short as possible|
| Content | Perform an application and documentation audit to [replace instances](https://github.com/GSA/notifications-admin/issues/631) of `U.S. Notify` with `Notify.gov` | Reflect a more streamlined brand
| Engineering | Begin implementation of [E2E tests](https://github.com/GSA/notifications-admin/issues/591); Implement beta.notify.gov [landing page](https://github.com/GSA/notifications-admin/issues/590); Finalize the agreement info and message limit handling ADRs for data model updates | Prepare site for public launch after LATO, make the data model align with our vision, enable automated replies for first partner, work towards a more reliable application |
| UX | Start [user testing interviews](https://github.com/GSA/notifications-admin/issues/592) and feedback; Kick off internal message recipient [opt-out test](https://github.com/GSA/notifications-admin/issues/395); Continue to iron out details with the [send message flow wireframes](https://github.com/GSA/notifications-admin/issues/573) | Gain feedback on usability and functionality, streamline confusing flows and processes |
| Content | Continue contributing to the strategy of the newly forming Content sub-team as we can (our focus is more on user testing this sprint) | Clearer understanding of roles and responsibilities on content strategy |
| Security | Respond to any assessment questions and/or needs | Keep the LATO award timeline as short as possible
| Engineering | Implement beta.notify.gov [landing page strategy](https://github.com/GSA/notifications-admin/issues/566); work towards completion of ["smart retention quotas"](https://github.com/GSA/notifications-api/issues/295) by [updating the data model](https://github.com/GSA/notifications-api/issues/141) ; document, configure, and test [auto-reply](https://github.com/GSA/notifications-api/issues/271) messages for demo phone number; explore [stress testing](https://github.com/GSA/notifications-api/issues/87) and [end-to-end tests](https://github.com/GSA/notifications-admin/issues/549) | Prepare site for public launch after LATO, make the data model align with our vision and progress towards higher daily messag send capability, enable automated replies for first partner, work towards a more reliable application |
| UX | Recruit usability testers; kick-off user testing in earnest; [propose new flows and wireframes](https://github.com/GSA/notifications-admin/issues/455) (remains from last sprint); | Gain feedback on usability and functionality, streamline confusing flows and processes |
| Content | Contribute to the strategy of the newly forming Content sub-team | Clearer understanding of roles and responsibilities on content strategy |
| Security | Respond to any assessment questions and/or needs | Keep the LATO award timeline as short as possible
| Engineering | Employ ["smart" retention](https://github.com/orgs/GSA/projects/20/views/1?pane=issue&itemId=30230455) for daily quota; align [delivery receipt UI display](https://github.com/GSA/notifications-admin/issues/536) with user expectations; finalize [timezone implementation](https://github.com/GSA/notifications-admin/issues/525) in UI | Maximize the amount of messages a partner can send in a given day; have intuitive and clear display of delivery success/failure and timestamps |
| UX | Rework the [navigation structure](https://github.com/GSA/notifications-admin/issues/535); [propose new flows and wireframes](https://github.com/GSA/notifications-admin/issues/455); propose a user-testing strategy | Simpler user navigation of the site, ongoing collection of user feedback for improvement |
| Content/Design/Engineering | Design and implement the public aspect of beta.notify.gov launch site | A simple display that clearly notes the site is in pilot/beta phase |
| Security | Respond to any assessment questions and/or needs | Keep the LATO award timeline as short as possible
| Engineering | Moving from an ad-hoc "complete must-haves" process to a more strategic, themed progression; examining and implementing a structure for [Architecture Decision Records](https://github.com/GSA/notifications-admin/issues/522); assessing and planning for timezone accommodations in both [back-end](https://github.com/GSA/notifications-api/issues/260) and [UI](https://github.com/GSA/notifications-admin/issues/525) | Less context-switching; better documentation and prioritization; a clear strategy and content regarding timezones for users |
| UX | Wrap first iteration of [USWDS component migration](https://github.com/GSA/notifications-admin/issues/453); [propose new flows and wireframes](https://github.com/GSA/notifications-admin/issues/455) | A U.S. government look and feel; easier user navigation |
| Content | [Hone content](https://github.com/GSA/notifications-admin/issues/523) for [U.S. Notify-specific aspects](https://github.com/GSA/notifications-admin/issues/521); finalize [style and terminology docs](https://github.com/GSA/notifications-admin/issues/481) | Clear and applicable documentation and direction in the application |
| Engineering | [Finalizing "must haves"](https://github.com/GSA/notifications-admin/issues/235) and moving to ["quality of life"](https://github.com/GSA/notifications-admin/issues/412) components, work on [data structure](https://github.com/GSA/notifications-api/issues/162) & clearing path to [promote services](https://github.com/GSA/notifications-admin/issues/301) to "live mode" | A functional application that allows for promotion from trial mode to external recipients |
| UX | Continue [integrating USWDS](https://github.com/GSA/notifications-admin/issues/453), start wireframing new flows, strategize collection and synthesis of partner feedback | A U.S. government look and feel, better accessibility, better experience |
| Content | [Content strategy](https://github.com/GSA/notifications-admin/issues/481) and [Notify terminology work](https://github.com/GSA/notifications-admin/issues/480), aligning with Studio comms strategy | Consistency in terminology, tone, type of content |
| Security | Respond to any assessment questions ASAP, transition duties to Steven | Keep the LATO award timeline as short as possible, ensure a smooth transition for compliance POC
| Engineering | Focus effort on Pilot "Must Haves", settle on a retention strategy | A usable, functioning MVP that meets LATO restrictions while maximizing message volume and experience |
| UX | Remove unnecessary components from existing site, create strategy to implement USWDS and begin migrating components. | A better, more simple experience that will start to accomplish a common look and feel as well as meet accessibility standards. |
| Content | Execute low-lift content tweaks; make necessary decisions and begin medium-to-high effort changes based on audit recommendations. | Future users will have at least logical content and documentation to follow, that reflects actual quotas and is applicable to U.S. Notify. |
| Security | Respond to any assessment questions ASAP, shore up docs, transition to new POC | Keep the LATO award timeline as short as possible, prepare for Ryan's rolling off the project |
| Engineering | Tackle data retention and message delivery receipts | Expand user capabilities while remaining LATO compliant. Give users ability to easily view failed messages. |
| UX | Audit & create a plan for implementing some “low-hanging fruit” aspects of USWDS | Understand similarities between UK Design and USWDS. Scope lift and path to allow team to schedule migration. |
| Content | Audit current content and recommend short-term content changes | Eliminate unnecessary/confusing content and add clarity to improve UX for pilot partners. |
| Security | Complete tasks to get assessment and begin assessment | Complete LATO docs to move us closer to LATO award and thus, piloting in earnest. |
