mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-03-12 06:12:28 -04:00
8.8 KiB
8.8 KiB
Notify Sprint Goals Log
Sprint: L (6/7/23)
| Goals | Impact | |
|---|---|---|
| Engineering | Employ "smart" retention for daily quota; align delivery receipt UI display with user expectations; finalize timezone implementation 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; propose new flows and wireframes; 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 |
Sprint: Kiwi (5/24/23)
| Goals | Impact | |
|---|---|---|
| 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; assessing and planning for timezone accommodations in both back-end and UI | Less context-switching; better documentation and prioritization; a clear strategy and content regarding timezones for users |
| UX | Wrap first iteration of USWDS component migration; propose new flows and wireframes | A U.S. government look and feel; easier user navigation |
| Content | Hone content for U.S. Notify-specific aspects; finalize style and terminology docs | Clear and applicable documentation and direction in the application |
| Security | Respond to any assessment questions and/or needs | Keep the LATO award timeline as short as possible |
Sprint: Jabiru (5/11/23)
| Goal | Impact | |
|---|---|---|
| Engineering | Finalizing "must haves" and moving to "quality of life" components, work on data structure & clearing path to promote services to "live mode" | A functional application that allows for promotion from trial mode to external recipients |
| UX | Continue integrating USWDS, 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 and Notify terminology work, 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 |
Sprint: Ibis (4/27/23)
| Goal | Impact | |
|---|---|---|
| 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 |
Sprint: Heron (4/13/23)
| Goal | Impact | |
|---|---|---|
| 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. |