Uploaded image for project: 'SAFe Solution'
  1. SAFe Solution
  2. SS-142

AA0.5 software configuration & deployment

    XporterXMLWordPrintable

Details

    Attachments

      Issue Links

        Parent Of

        Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-4296 Establish and standardise environment representative directory structure for storing configuration data for deployments, and deployment mechanisms that use this structure, for AA0.5

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

        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-4364 Production Notebooks

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

        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-4365 Kyverno: put on enforcer mode

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

        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-3099 CAR Caching proxies for upstream dependent artefacts for python packages

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

        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-3100 CAR Caching proxies for upstream dependent artefacts for helm charts

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

        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-3267 Support C++ Projects in Pipeline Machinery

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

        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-4076 Image delivery, validation, cache priming and shipping

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

        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-4369 Automatic generation of SBOMs for built artefacts

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

        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-4399 Establish an MVP set of UML symbols that can be used to communicate graphically the function and form of each of the PBS items, for Web UI and GUI use

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

        Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3700 Design and management of etcd deployment within the SDP for AA0.5

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

        Spike - A time limited investigation to get some knowledge SP-4200 Investigate ODA use case and data replication

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

        Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-4297 Establish the Mid AA0.5 deployment repository

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

        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-4372 Deployment Management

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

        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-2278 Application Configuration SSoT

        • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
        • Program Backlog

        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-4232 MCCS control system monitoring and alarms

        • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
        • Program Backlog

        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-4370 Dish.LMC define deployment mechanism and deploy to dish HW

        • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
        • Program Backlog

        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-4202 EDA, ElasticSearch, TangoDB deployed as managed services

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

        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-4117 Dish.LMC implementation of the DVS Proxy, support integration and verification of the 1st dish using the DVS system

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

        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-4366 Hand over Low platforms to AIV for use

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

        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-4367 Institute patching routine for CICD machinery

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

        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-4368 Improved Environment Management for CICD and integration

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

        Page Loading...

        Page Loading...

        Page Loading...

        Features

        Structure

          Activity

            People

              A.DeBeer De Beer, Adriaan
              b.mort Mort, Ben
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Feature Progress

                Story Point Burn-up: (0%)

                Feature Estimate: 10.0

                IssuesStory Points
                To Do00.0
                In Progress   2133.5
                Complete00.0
                Total2133.5

                Capability Progress

                  Feature Point Burn-up: (0%)

                  Capability Estimate: 10

                  CountFeature Points
                  Todo1724
                  In Progress   416
                  Done00
                  Total2132

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel