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

Deliver a design for the next iteration of the GMS

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

Details

    • SRCnet
    • Hide

      GMS is a cause of contention amongst SRCNet contributors.

      • Hosting is not yet sustainable
      • Is the GMS required for v0.1 operations?
      • If so, is the current implementation functional and performant enough for all v0.1 activities?
      • Could GMS sit in API space? What are the alternative approaches?
      • How should group membership be expressed?
      • etc.

      This spike is to make a decision on what the next iteration of GMS shall be.

      Note that the answer might be to keep the current approach!

       

      Show
      GMS is a cause of contention amongst SRCNet contributors. Hosting is not yet sustainable Is the GMS required for v0.1 operations? If so, is the current implementation functional and performant enough for all v0.1 activities? Could GMS sit in API space? What are the alternative approaches? How should group membership be expressed? etc. This spike is to make a decision on what the next iteration of GMS shall be. Note that the answer might be to keep the current approach!  
    • Hide

      AC0: The architecture core group have reached consensus that the current GMS is sufficient for v0.1 operations

      OR

      AC1: Deliver a design for the next iteration of the GMS

      AC2: The architecture core group (+ a CADC rep) have given their consent for the design to be implemented. (consent is a lower threshold to reach than consensus)

      AC3: The required development features have been refined with BH, ACs approved by a PM (plus a priority and estimate if proposed to be worked on in PI25)

      Either direction must be shared with the ART

      Show
      AC0: The architecture core group have reached consensus that the current GMS is sufficient for v0.1 operations OR AC1: Deliver a design for the next iteration of the GMS AC2: The architecture core group (+ a CADC rep) have given their consent for the design to be implemented. (consent is a lower threshold to reach than consensus) AC3: The required development features have been refined with BH, ACs approved by a PM (plus a priority and estimate if proposed to be worked on in PI25) Either direction must be shared with the ART
    • 0.5
    • 0.5
    • 0
    • Team_SRCARCH
    • PI24-PB SRC23-PB service-integration

    Description

       

       

      Old title:

      ResolveResolve final question/ concern regarding expression of group membership by the GMS

       

      Old description:

      Follows on from SP-4106, SP-4105.

      See write up: https://confluence.skatelescope.org/display/SRCSC/SP-4105

      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-4872 AAA 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-4547 Add Group Management UI to the Science gateway

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Implementing
          relates to

          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-4455 GMS responsibility clarified, hosted service is stable for 0.1

          • 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...

          Structure

            Activity

              People

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

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 0.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel