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

Re-enable OET deployment and testing with SKAMPI

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

Details

    • True
    • Obs Mgt & Controls
    • Hide

      Lack of integration of OET along with system acceptance tests is potentially incurring technical debut due to the possible rework costs of choosing to only be testing with a standalone version. 

      Re-integration of OET, along with appropriate e2e system acceptance testing should mitigate this.

      Re-integration of OET will make the e2e system more usable for scripting and SB testing.

      Show
      Lack of integration of OET along with system acceptance tests is potentially incurring technical debut due to the possible rework costs of choosing to only be testing with a standalone version.  Re-integration of OET, along with appropriate e2e system acceptance testing should mitigate this. Re-integration of OET will make the e2e system more usable for scripting and SB testing.
    • Hide
      • Well defined OET release that passes all standalone OET (sub-)system-level tests
      • Identified, configured minimal release of OET deployable via system deployment scripts in SKAMPI
      • System-level acceptance tests development for SKAMPI that demonstrate successful deployment and integration of OET as part of an SKA software deployment and test minimal e2e functionality of the distributed control system
      Show
      Well defined OET release that passes all standalone OET (sub-)system-level tests Identified, configured minimal release of OET deployable via system deployment scripts in SKAMPI System-level acceptance tests development for SKAMPI that demonstrate successful deployment and integration of OET as part of an SKA software deployment and test minimal e2e functionality of the distributed control system
    • 2
    • 2
    • 40
    • 20
    • Team_BUTTONS
    • Sprint 5
    • Hide

      The first AC was met:

      • The code has been migrated to reflect new SKA standards
      • Integration tests have been created
      • A large proportion of the required new documentation has been prepared
      Show
      The first AC was met: The code has been migrated to reflect new SKA standards Integration tests have been created A large proportion of the required new documentation has been prepared
    • 13.6
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • Cross_Team_Code_Review
    • SPO-1547

    Description

      Re-enable a minimal version of OET for deployment integrated and tested with other (sub-)systems.

      Attachments

        Issue Links

          Child 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. SS-86 Reintegrate single software components into SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          is cloned 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-2356 Observational Execution of the basic instruction set of an OET script on Mid

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

          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-2327 CLONE - Re-enable OET deployment and testing with SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Discarded
          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-2262 Integration effort: End-to-End On/Off Command Test: OET → TMC → SDP

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                Adam.Avison Avison, Adam
                a.bridger Bridger, Alan
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete619.0
                  Total619.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel