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

Initial MCCS Engineering dashboard

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

Details

    • Feature
    • Must have
    • PI14
    • None
    • Obs Mgt & Controls
    • Hide

      Work to describe and outline a suitable Eng UI plan has concluded in PI-11.  This feature opportunistically continues this collaboration.
      Direct benefit acrues from obtaining a better tool to control and diagnose MCCS in development and use in PSI & labs.

      Show
      Work to describe and outline a suitable Eng UI plan has concluded in PI-11.  This feature opportunistically continues this collaboration. Direct benefit acrues from obtaining a better tool to control and diagnose MCCS in development and use in PSI & labs.
    • Hide

      Example UI, Demo, feedback from potential users.

      Show
      Example UI, Demo, feedback from potential users.
    • 2.5
    • 1
    • 20
    • 8
    • Team_MCCS
    • Sprint 5
    • Hide

      The focus of this feature during this PI was establish a good candidate starting point fo implementing an MCCS focused Engineering UI which would serve MCCS as its functionality evolved but also was created in the spirit of the SKA UI experience. A number of interviews were held to ascertain different stakeholders points of view, including potential end system users and current MCCS developer to understand what areas of the software were sufficiently matured and would benefit from an initial UI to allow visual interactions. this lead to the formation of a wireframe to prepare for implementing in PI15. The key steps achieved in PI14 align to the ticket headlines stated below:
      MCCS-973 Identify areas of MCCS ready for a User Interface
      MCCS-974 MCCS User Story Interview
      MCCS-980 Wireframe User Interface
      MCCS-978 Identify first MCCS dashboard to build
      MCCS-1007 investigating the difference between Eng UI and ITF UI

      Show
      The focus of this feature during this PI was establish a good candidate starting point fo implementing an MCCS focused Engineering UI which would serve MCCS as its functionality evolved but also was created in the spirit of the SKA UI experience. A number of interviews were held to ascertain different stakeholders points of view, including potential end system users and current MCCS developer to understand what areas of the software were sufficiently matured and would benefit from an initial UI to allow visual interactions. this lead to the formation of a wireframe to prepare for implementing in PI15. The key steps achieved in PI14 align to the ticket headlines stated below: MCCS-973 Identify areas of MCCS ready for a User Interface MCCS-974 MCCS User Story Interview MCCS-980 Wireframe User Interface MCCS-978 Identify first MCCS dashboard to build MCCS-1007 investigating the difference between Eng UI and ITF UI
    • 14.6
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

    Description

      Create initial test Main-level engineering dashboard, following work developed in PI-11 (continue collaboration with CREAM)

      Attachments

        Issue Links

          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-2488 CLONE - Initial MCCS Engineering dashboard PI15

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

          Page Loading...

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                m.waterson Waterson, Mark
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete516.0
                  Total516.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel