| Engineering | Change timezones displays to [Eastern time](https://github.com/GSA/notifications-admin/issues/861), [create properties on org model](https://github.com/GSA/notifications-api/issues/331) to process agreement info | Better timezone familiarity, continuity between application orgs and agreements | Building Notify.gov |
| UX | Begin [re-thinking Notify IA](https://github.com/GSA/notifications-admin/issues/910), create a synthesis of partner feeback thusfar, wireframe a more [user-friendly dashboard](https://github.com/GSA/notifications-admin/issues/889), send [Notify logo](https://github.com/GSA/notifications-admin/issues/859) proposal to begin approvals, add UI consideration regarding [multi-lingual messages](https://github.com/GSA/notifications-admin/issues/901) | Improve ease of use, begin process of brand creation | Obtain approval for logo/brand|
| Security | Complete pre-requisite documentation, start project planning timelines and control group deadlines | Aim to have package completed with enough time to allow for long assessment| Secure ATO |
| Content | Finalize cloud.gov pages IAA mod for content site | Enable an easy static website for future content | Building Notify.gov |
| Ops | Complete Beverly's onboarding with necessary access to cloud.gov, AWS, and other tools| Add valuable dev resources to increase our capacity
| Engineering | Continue login.gov [sandbox implementation](https://github.com/GSA/notifications-admin/issues/338), catch up deploys that lag from last week's dependency audit failures, change timezones displays to [Eastern time](https://github.com/GSA/notifications-admin/issues/861), Persist [individal send reports](https://github.com/GSA/notifications-admin/issues/855) somwehere in the app| Stronger auth security, streamlined UX, better timezone familiarity |
| UX | Continue making common-sense [UI/UX changes](https://github.com/GSA/notifications-admin/issues/828), review and finalize proposal for [Notify logo](https://github.com/GSA/notifications-admin/issues/859) & begin approvals chain | Improve ease of use, begin process of brand creation |
| Security | Complete pre-requisite documentation, start project planning timelines and control group deadlines | Aim to have package completed with enough time to allow for long assessment|
| Content | Finalize cloud.gov pages IAA mod for content site | Enable an easy static website for future content |
| Ops | Onboard Beverly, get access to tools for them once possible | Add valuable dev resources to increase our capacity
| Engineering | Shift the quota count from `service` to `org`, complete [notify.gov redirect](https://github.com/GSA/notifications-api/issues/515), continue login.gov [sandbox implementation](https://github.com/GSA/notifications-admin/issues/338), meet with AWS to gain answers on opt-out capabilities| Stronger auth security, streamlined UX, operational efficiency |
| UX | Make common-sense [UI/UX changes](https://github.com/GSA/notifications-admin/issues/828), Complete proposal for [Notify logo](https://github.com/GSA/notifications-admin/issues/859), switch application to Eastern timezone displays | Improve ease of use, begin process of brand creation |
| Security | Complete pre-requisite documentation, start project planning timelines and control group deadlines | Aim to have package completed with enough time to allow for long assessment|
| Content | Work on cloud.gov pages IAA mod for content site | Enable an easy static website for future content |
| Ops | Onboard new back-end dev, get access to tools for them once possible | Add valuable dev resources to increase our capacity
| Engineering | Finish retention and [quota strategy](https://github.com/GSA/notifications-api/issues/443), obtain access to [Login.gov sandbox](https://github.com/GSA/notifications-admin/issues/338) and begin integration work, tend to remaining low/medium bugs, request more toll-free [partner numbers](https://github.com/GSA/notifications-admin/issues/764), create a formal [manual qa script](https://github.com/GSA/notifications-admin/issues/809) | Greater sending volume for partners, start down path of ATO-required auth solution |
| UX | Perform observational and formal user feedback sessions with partners to inform flow and look/feel redesign, surface and remedy straightforward UI changes | Inform future features, flow, and feel of the application |
| Security | Complete pre-requisite documentation, start project planning timelines and control group deadlines | Aim to have package completed with enough time to allow for long assessment|
| Content | Work on cloud.gov pages IAA mod for content site | Enable an easy static website for future content |
| Ops | Onboard new back-end dev, get access to tools for them, meet with POC and team, get them oriented to start work | Add valuable dev resources to increase our capacity
| Engineering | Resolve High and Urgent [bugs](https://github.com/GSA/notifications-admin/issues/758), remove cloud.gov [auth wall](https://github.com/GSA/notifications-admin/issues/679), [redirect](https://github.com/GSA/notifications-admin/issues/680) notify.gov to beta.notify.gov, change retention and [quota strategy](https://github.com/GSA/notifications-api/issues/443), begin scoping and obtain access to Login.gov sandbox | Ensure the best possible experience for first partner use, start down path of ATO-required auth solution |
| UX | Perform observational and formal user feedback sessions with partners to inform flow and look/feel redesign, surface and remedy straightforward UI changes | Inform future features, flow, and feel of the application |
| Security | Align personnel to begin ATO | Source adequate resources to begin process|
| Content | Kick off cloud.gov pages IAA for content site | Enable an easy static website for future content
| Engineering | Continue app stabilization efforts, including: [Completing UK stylesheet removal](https://github.com/GSA/notifications-admin/issues/686), [Removing GDS libraries](https://github.com/GSA/notifications-admin/issues/674), and working to improve documentation | Increase app reliability and simplicity prior to first partner use |
| UX | Hone a visual brand strategy for proposal to leadership, ensure that USWDS elements are rendering properly | Consistent look and feel for Notify.gov, smooth, non-glitchy experience for users |
| Security | Begin scoping and planning for addressing LATO findings | Complete resolving POA&Ms in their designated timeline|
| Content | Use research and user test information to begin crafting more concise content | Have content ready for later addition to the site
| Engineering | (Due to low engineering availability, the goals from last sprint continue) 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 | Analyze data gathered from user-testing and propose changes from that analyzation; Hone a visual brand strategy for proposal to leadership | Improve upon oft-identified user barriers; create a consisten look and feel for Notify.gov |
| Security | Respond to any assessment questions and/or needs (assessment is nearing end) | Keep the LATO award timeline as short as possible|
| Content | Collate research to inform future best practices content | Have content ready for later addition to the site
| 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 |
| Content | Perform an application and documentation audit to [replace instances](https://github.com/GSA/notifications-admin/issues/631) of `Notify.gov` 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 [Notify.gov-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 Notify.gov. |
| 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. |
