Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Must have
Fix Version/s: PI13, PI14
Component/s: None
Labels:
- mccs_firmware
- mccs_software

ARTs:

Obs Mgt & Controls
Benefit hypothesis:

Hide

Deployment of MCCS to control AAVS in PI 14 is essential to support the AA0.5 Roadmap. This covers planning and if possible addresses any issues.

Show
Deployment of MCCS to control AAVS in PI 14 is essential to support the AA0.5 Roadmap. This covers planning and if possible addresses any issues.
Acceptance criteria:

Hide

Identification of minimum essential behaviour & performance

Plan to implement needed work.

Show
Identification of minimum essential behaviour & performance Plan to implement needed work.
Feature Points:
5.8
Initial Size:
5.8
Cost of Delay:
20
WSJF:
3.448
Epic Link:
LFAA Development and MVP Integration
Agile Teams:

Team_MCCS
Due Sprint:
Sprint 4
Story Point Burn-up:
Overdue:
Outcomes:

Hide

Identification of minimum essential behaviour & performance.

During the mid point of PI13, the MCCS team participated in a workshop to examine what we had in hand vs what we wish to have available for deployment on AAVS. This has helped the team to align our thoughts on what we need to concentrate on for the remainder of PI13, but equally importantly gaining an idea of what we need to prioritise for PI14. This was captured in https://confluence.skatelescope.org/x/9YoNCg

Plan to implement needed work.
Following the workshop activities the team embarked on trying to complete enabling work to allow us to be prepared to proceed with our plan through PI14

Show
Identification of minimum essential behaviour & performance. During the mid point of PI13, the MCCS team participated in a workshop to examine what we had in hand vs what we wish to have available for deployment on AAVS. This has helped the team to align our thoughts on what we need to concentrate on for the remainder of PI13, but equally importantly gaining an idea of what we need to prioritise for PI14. This was captured in https://confluence.skatelescope.org/x/9YoNCg Plan to implement needed work. Following the workshop activities the team embarked on trying to complete enabling work to allow us to be prepared to proceed with our plan through PI14
Resolved PI.Sprint:
14.2

Feature Checklist:

Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

Demos:
- OMC_ART_SystemDemo_4
Requirement Status:

PI22 - UNCOVERED
Labels_MIRO:
mccs_firmware mccs_software

Description

There has been much effort in the past 4 PIs to bridge the gaps between the requirements of the MCCS software and that which exists and has been demonstrated to work successfully for AAVS. However as we draw closer towards deploying MCCS on AAVS there is a need to understand and plan for any of the remaining implementation gaps. By the start of PI14 the project, and more specifically MCCS, needs to know what is missing in the MCCS implementation which would prevent successful deployment on AAVS. From this analysis a scope of work (for PI14planning) is prepared.

Attachments

Issue Links

clones

SP-1971 Prepare to deploy to AAVS

Done

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...

Structure

Activity

People

Assignee:: Bridger, Alan

Reporter:: Braddock, Ralph

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 5.8

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	9	21.0
Total	9	21.0

Dates

Created:: 03/Nov/21 11:35 AM

Updated:: 15/Apr/24 9:46 AM

Resolved:: 30/Mar/22 9:59 AM

AAVS deployment - plan for control side