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

Initialisation of Minimal Viable Set of SRCNet Policies for v0.1

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

Details

    • SRCnet
    • Hide

      A pathway towards:

      • Informed planning / implementation / procurement of SRCNet software, networking, infrastructure...
      • Reduced bias and increased confidence in the SRCNet decision-making process
      • Empowered and consistent governance
      • Mitigation of risks regarding: security, data governance, resource management...
      • Providing assurance to SRCs & SKA and securing the reputation of all participants in SRCNet
      Show
      A pathway towards: Informed planning / implementation / procurement of SRCNet software, networking, infrastructure... Reduced bias and increased confidence in the SRCNet decision-making process Empowered and consistent governance Mitigation of risks regarding: security, data governance, resource management... Providing assurance to SRCs & SKA and securing the reputation of all participants in SRCNet
    • Hide
      • A group of initial policy-makers has been formed who can at least represent the v0.1 SRC sites
      • A minimum list of policies that will be required for v0.1 has been created
      • An existing set of policies have been adapted for SRCNet as our first draft
      • The policy concepts and an initial policy-making/changing process has been communicated / demoed to the SRCNet community
      • Outputs (including drafts) are made transparent i.e. documentation is available on / linked from SKA Confluence

      A Stretch Goal is to identify the interested/influential stakeholders per policy

      Show
      A group of initial policy-makers has been formed who can at least represent the v0.1 SRC sites A minimum list of policies that will be required for v0.1 has been created An existing set of policies have been adapted for SRCNet as our first draft The policy concepts and an initial policy-making/changing process has been communicated / demoed to the SRCNet community Outputs (including drafts) are made transparent i.e. documentation is available on / linked from SKA Confluence A Stretch Goal is to identify the interested/influential stakeholders per policy
    • Intra Program
    • 1
    • 1
    • 0
    • Team_PURPLE
    • Sprint 5
    • Hide

      Documented - https://confluence.skatelescope.org/x/-vVcE

      A policy roadmap has been agreed.

      Policy marker terminology and procedures are documented.

      Policy setting terminology and procedures have been documented.

      A list of required policies and their priority has been agreed.

      Demo https://confluence.skatelescope.org/x/E33YDw

      The list of policy-endorsers is still required before sign-off.

       

      Show
      Documented - https://confluence.skatelescope.org/x/-vVcE A policy roadmap has been agreed. Policy marker terminology and procedures are documented. Policy setting terminology and procedures have been documented. A list of required policies and their priority has been agreed. Demo https://confluence.skatelescope.org/x/E33YDw The list of policy-endorsers is still required before sign-off.  
    • 22.6
    • Accepted by FO

    • PI24 - UNCOVERED

    • policy

    Description

      Here we Initialise a Minimal Viable Set of SRCNet Policies for v0.1

      Next PI (23), the Policy feature is SP-4135 to mature / establish the contents of the initial versions of SRCNet policies.

      The following PI (24) is intended to include this Policy feature SP-4136 to assess initial complience (which isn't expected to be 100% at this stage) and identify mitigations.

      See confluence!  https://confluence.skatelescope.org/x/-vVcE

      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-4870 Science Enabling v0.1 - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Implementing
          is required 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-4135 Establishment of Baseline SRCNet Security Agreements

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                Robert.Perry Perry, Robert
                Robert.Perry Perry, Robert
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (57.14%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do23.0
                  In Progress   00.0
                  Complete44.0
                  Total67.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel