notifications-admin/docs/sprint-goals.md

Notify Sprint Goals Log

Sprint: B (1/18/24)

2024 Sprints will be named after mythical creatures

	Goals	Impact	Milestone(s)
Engineering	Get staging stable and bugs fixed in order to do a prod push, finalize Login.gov implementation, complete epic to remove phone numbers from db, calculate pre-send message parts to add to confirmation page, finish E2E testing implementation, set up opt-out lists by phone number	Install required auth, expand message send volume for partners, allow users to see how many parts a send will cost, improve app stability, partition opt-outs so that they aren't across the system	Building Notify.gov
UX	Tackle Usage and Performance epic as highest priority group of user stories, break out UX work into more user-stories and correlating epics, prioritize epic/story order, improve pre-send confirmation page	Improve UX	Building Notify.gov
Security	Complete necessary control families	Aim to have package completed with enough time to allow for long assessment	Secure ATO
Content	Get refreshed content for Using Notify pages in place, make content more clear about limits, make content clearer by adding parts where necessary	Improve clarity of message parts for users, bring existing content into current state	Building Notify.gov
Ops	Assist in Tech to Gov process, plan gap coverage for Tim's departure 2/9

Sprint: Akhlut (1/3/24)

2024 Sprints will be named after mythical creatures

	Goals	Impact	Milestone(s)
Engineering	Continue identifying, fixing, and displaying various applicable message part limits, devise ways to create better access to reports, implement Login.gov on staging environment, advance epic to remove phone numbers from db	Better track annual and smart-retention limits, install required auth, make reports easier to find, expand message send volume for partners	Building Notify.gov
UX	Spin up weekly redesign syncs, identify necessary dashboard metrics to visualize, improve team member section	Improve UX	Building Notify.gov
Security	Complete necessary control families	Aim to have package completed with enough time to allow for long assessment	Secure ATO
Content	Finish making editing content easier with existing templates, finalize decision on terminology regarding batch/campaign/job, make content more clear about limits, make content clearer by adding parts where necessary	Improve clarity of message parts for users, streamline content editing for the team	Building Notify.gov
Ops	Assist in Tech to Gov process

Sprint: Zoe's Imperial Pigeon (12/21/23)

Sprint velocity was very low due to holiday OOO

	Goals	Impact	Milestone(s)
Engineering	Spend time identifying, fixing, and displaying various applicable message part limits, devise ways to create better access to reports, implement Login.gov on staging environment, advance epic to remove phone numbers from db	Better track annual and smart-retention limits, install required auth, make reports easier to find, expand message send volume for partners	Building Notify.gov
UX	Re-think Notify IA, start implementing dashboard changes, improve team member section	Improve UX	Building Notify.gov
Security	Complete necessary control families	Aim to have package completed with enough time to allow for long assessment	Secure ATO
Content	Make content more clear about limits, make content clearer by adding parts where necessary, test making editing content easier with existing templates	Improve clarity of message parts for users, streamline content editing for the team	Building Notify.gov
Ops	Assist in Tech to Gov process

Sprint: Xingu Scale-Backed Antbird (12/6/23)

(Sprint X was canceled due to Thanksgiving, so this is X & Y)

	Goals	Impact	Milestone(s)
Engineering	Spend time identifying, fixing, and displaying various applicable message part limits, devise ways to create better access to reports, implement Login.gov on staging environment	Better track annual and smart-retention limits, continuity between application orgs and agreements	Building Notify.gov
UX	Re-think Notify IA, start implementing dashboard changes, obtain requested user feedback on Notify logo proposal	Improve ease of use, begin process of brand creation	Obbtain approval for logo/brand
Security	Complete CP family of controls, Draft config management plan	Aim to have package completed with enough time to allow for long assessment	Secure ATO
Content	Make content (and MOUs) more clear about limits, test making editing content easier with existing templates	Improve clarity of message parts for users, streamline content editing for the team	Building Notify.gov
Ops

Sprint: Wallcreeper (11/8/23)

(Sprint is at low capacity due to Thanksgiving week)

	Goals	Impact	Milestone(s)
Engineering	Change timezones displays to Eastern time, create properties on org model to process agreement info	Better timezone familiarity, continuity between application orgs and agreements	Building Notify.gov
UX	Begin re-thinking Notify IA, create a synthesis of partner feeback thusfar, wireframe a more user-friendly dashboard, send Notify logo proposal to begin approvals, add UI consideration regarding multi-lingual messages	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

Sprint: Velvety Black Tyrant (10/30/23)

	Goals	Impact
Engineering	Continue login.gov sandbox implementation, catch up deploys that lag from last week's dependency audit failures, change timezones displays to Eastern time, Persist individal send reports somwehere in the app	Stronger auth security, streamlined UX, better timezone familiarity
UX	Continue making common-sense UI/UX changes, review and finalize proposal for Notify logo & 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

Sprint: Upupa Marginata (10/12/23)

	Goals	Impact
Engineering	Shift the quota count from service to org, complete notify.gov redirect, continue login.gov sandbox implementation, meet with AWS to gain answers on opt-out capabilities	Stronger auth security, streamlined UX, operational efficiency
UX	Make common-sense UI/UX changes, Complete proposal for Notify logo, 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

Sprint: Toucan (9/28/23)

	Goals	Impact
Engineering	Finish retention and quota strategy, obtain access to Login.gov sandbox and begin integration work, tend to remaining low/medium bugs, request more toll-free partner numbers, create a formal manual qa script	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

Sprint: Snowy Owl (9/14/23)

	Goals	Impact
Engineering	Resolve High and Urgent bugs, remove cloud.gov auth wall, redirect notify.gov to beta.notify.gov, change retention and quota strategy, 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

Sprint: Rook (8/31/23)

(Sprint planning cancelled)

Sprint: Quetzal (8/17/23)

	Goals	Impact
Engineering	Continue app stabilization efforts, including: Completing UK stylesheet removal, Removing GDS libraries, 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

Sprint: Puffin (8/3/23)

	Goals	Impact
Engineering	(Due to low engineering availability, the goals from last sprint continue) Reduce technical debt and stabilize application; carry out rigorous testing of features and infrastructure; solve known bugs	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

Sprint: Osprey (7/19/23)

	Goals	Impact
Engineering	Reduce technical debt and stabilize application; carry out rigorous testing of features and infrastructure; solve known bugs	Increase app reliability prior to first partner use
UX	Continue user testing interviews and feedback; Kick off internal message recipient opt-out test	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 of Notify.gov with Notify.gov	Reflect a more streamlined brand

Sprint: Northern Screamer (7/5/23)

	Goals	Impact
Engineering	Begin implementation of E2E tests; Implement beta.notify.gov landing page; 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 and feedback; Kick off internal message recipient opt-out test; Continue to iron out details with the send message flow wireframes	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

Sprint: Merlin (6/22/23)

	Goals	Impact
Engineering	Implement beta.notify.gov landing page strategy; work towards completion of "smart retention quotas" by updating the data model ; document, configure, and test auto-reply messages for demo phone number; explore stress testing and end-to-end tests	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 (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

Sprint: Lazuli Bunting (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 Notify.gov-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 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

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.