013 - Developing An MVP For The Data Management Service

[eveleighoj]

1. Introduction

The data management team currently manage all of the configuration for data feeding into the platform via a github hub repo (config). While this process is workable it requires developers to add data and isn't a scaleable approach.

Instead this should be managed via an application and utilise the async-rrquest-backend to complete the required tasks.

It's useful to know that a prototype app has already been created called the config-manager and an be used as a base app to build on.

The Users are internal staff. any functioality developed in the async processor can be applied to the povide sevice at a later date but it must be optional as not to affect the running service.

other links:

• https://mhclg-my.sharepoint.com/:w:/g/personal/ben_hodgkiss_communities_gov_uk/EU6v3qpLCilOh6Q07UlPpxwBv1_qBFeo6iyHJBppbYEFGg?wdOrigin=TEAMS-MAGLEV.p2p_ns.rwc&wdExp=TEAMS-TREATMENT&wdhostclicktime=1749462880206&web=1

3. User Stories and Epics

   • Epics (broad user needs or themes)
   • User stories (format: "As a [user], I want [function] so that [benefit]")
   • Acceptance criteria for each story
   • Prioritized backlog items

4. Business Objectives

   • Key goals tied to DM value, platform coverage
   • Success metrics (e.g., speed of adding data, exception work time saved impact)
   • Minimum Viable Product (MVP) definition

5. Stakeholder Engagement

   • Stakeholder map (users, team, sponsors)
   • Collaboration plan (e.g., sprint reviews, daily standups)
   • Feedback loops and communication channels

6. Current State Snapshot

   • Brief overview of existing processes or systems
     • Add Data Tool - Business Analysis config#728
   • Key pain points or opportunities
   • Relevant data or user feedback

7. Future State Sketch

   • High-level solution concept (e.g., wireframes, user flows)
   • Incremental delivery plan (what’s delivered in each sprint)
   • Expected benefits for users and business (tool be used by non developer)

8. Risks and Assumptions

   • Key risks or blockers to delivery
   • Assumptions about users, technology, or resources
     • (must be able to work on a standard MHCLG Laptop)
   • Mitigation or validation approaches (e.g., prototyping, testing)

9. Iteration and Delivery Plan

   • Sprint goals and cadence
     • 4 week sprints
   • Initial backlog prioritization (MoSCoW or similar)
   • Dependencies and resource needs

10. Supporting Artifacts

• Persona definitions (if applicable)
• Story maps or process flows
• Glossary or reference materials
  TBD

[neilfwar]

@RayNorton - Wondering if we can put some dates on tickets for checking progress against some of the priority items in headings 1-9 listed ? I will put some time for us to discuss & agree.

[RayNorton]

@neilfwar I've broken down some elements that I need to put in, maybe we can catch up?
AGILE.xlsx

[neilfwar]

@RayNorton in case you have may have not captured - here are some MVP requirements I noted down from various discussions

MVP
• Building and Hosted similar to Check tool design
• MHCLG laptop as typical user
• User friendly to allow user to compare data table visually as with check tool
• Which data sets? - All Datasets
• Push button to make add newly added data live with without PR, but need log files to show who, what has or has not been done
• Exception bucket for edge cases to manually work - we need to define these more so will get a call booked
• Ability to allow users to abort mid way in adding data ie if missing vital info so unable to continue

[gmatchett]

@Swati-Dash @Ben-Hodgkiss have you seen this https://github.com/user-attachments/files/20865587/AGILE.xlsx