Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4318

Consolidate Fragmented SRCNet User Artefacts (cases, stories, journeys, flows, personas)

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      SRCNet user stories, journeys, flows and personas are currently fragmented across multiple artefacts.
      IBNLT a use case document, team confluence pages, AAI cookbook, architecture branch on confluence, SRC requirements Jira, SRCNet "useful documents" etc.

      Hence efforts are being duplicated, the status/relevance of each artefact is not clear, and most importantly the value of these artefacts is not being realised.

      Consolidating each category of user artefacts into a single, live, shared, source of truth will: provide powerful, actionable insight into the SRCNet user base, their needs and expectations.

      Show
      SRCNet user stories, journeys, flows and personas are currently fragmented across multiple artefacts. IBNLT a use case document, team confluence pages, AAI cookbook, architecture branch on confluence, SRC requirements Jira, SRCNet "useful documents" etc. Hence efforts are being duplicated, the status/relevance of each artefact is not clear, and most importantly the value of these artefacts is not being realised. Consolidating each category of user artefacts into a single, live, shared, source of truth will: provide powerful, actionable insight into the SRCNet user base, their needs and expectations.
    • Hide

      AC 0: A discovery exercise is done to find all of the applicable work completed so far. Each has been assessed for relevance moving forwards. Retire those that are no longer needed / so out of date they will be quicker to rewrite.

      AC 1: For each user artefact "category" a single, shared, live source of truth has been established ~(cases, stories, journeys, flows, personas). Each of these homes is easily discoverable via SRCNet confluence.

      AC 2: Each category has a clearly defined definition that:

      • distinguishes it from the others
      • explains how the contents are translated into actions (e.g. NFRs, system/version requirements)
      • explains how they relate to other artefacts e.g. the product roadmap, architecture diagrams
      • communicates / links to chosen standards, templates, methodologies

      AC 3: Given the above and the establishment of https://ska-telescope.gitlab.io/src/kb/ska-src-docs-operator/ the future of the cookbook has been agreed.

      AC 4: Each category is populated with the latest version of the current contents. Duplication and contradictions must be resolved. Otherwise, no new content is required.

      AC 5: All of the above is socialised with the ART, explaining that these are now the official SRCNet versions.

      AC 6: Old artefacts / versions are retired.

      (Stretch) AC 7: Ownership of these artefacts has been discussed, including the remit of the expected Science Delivery (value stream) team from PI25 onwards.

      (Stretch) AC 8: further develop these user artefacts with the addition of user-flows per user-persona (original feature)

      Show
      AC 0: A discovery exercise is done to find all of the applicable work completed so far. Each has been assessed for relevance moving forwards. Retire those that are no longer needed / so out of date they will be quicker to rewrite. AC 1: For each user artefact "category " a single, shared, live source of truth has been established ~(cases, stories, journeys, flows, personas). Each of these homes is easily discoverable via SRCNet confluence. AC 2: Each category has a clearly defined definition that: distinguishes it from the others explains how the contents are translated into actions (e.g. NFRs, system/version requirements) explains how they relate to other artefacts e.g. the product roadmap, architecture diagrams communicates / links to chosen standards, templates, methodologies AC 3: Given the above and the establishment of https://ska-telescope.gitlab.io/src/kb/ska-src-docs-operator/ the future of the cookbook has been agreed. AC 4: Each category is populated with the latest version of the current contents. Duplication and contradictions must be resolved. Otherwise, no new content is required. AC 5: All of the above is socialised with the ART, explaining that these are now the official SRCNet versions. AC 6: Old artefacts / versions are retired. (Stretch) AC 7: Ownership of these artefacts has been discussed, including the remit of the expected Science Delivery (value stream) team from PI25 onwards. (Stretch) AC 8: further develop these user artefacts with the addition of user-flows per user-persona (original feature)
    • Inter Program
    • 4
    • 4
    • 0

    • Feature SP-4131 Complete and socialise user stories for SRCNet 0.1 (AAI)

    • Team_TANGERINE
    • Sprint 5
    • Hide

      https://confluence.skatelescope.org/x/SuOJEQ

      Show
      https://confluence.skatelescope.org/x/SuOJEQ

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.x science-gateway

    Description

       

      Old text before rewriting the feature:

       

      After the creation of the user personas, an activity will be started to draw out the user journeys (or flows). The goal of this mapping is to show how each of the personas will use the system, and where they interact with what component.

      In essence, the UX analysis is always covering the next version of tooling. However since there is no user journey at the moment, this feature will inform SRCNet v0.1 as well as future incarnations of the system.

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4869 Science Gateway v0.1 - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Implementing
          is duplicated by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4633 Define end-to-end SRCNet user flows

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          is informed by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4131 Complete and socialise user stories for SRCNet 0.1 (AAI)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Structure

            Activity

              People

                Robert.Perry Perry, Robert
                Y.Grange Grange, Yan
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (44.44%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do11.0
                  In Progress   24.0
                  Complete44.0
                  Total79.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel