Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Medium
Fix Version/s: PI24
Component/s: COM Software Services
Labels:
- Team_SYSTEM

ARTs:

Services
Benefit hypothesis:

Hide

System Team (ST) is working closely with Tango Developers for some time and now ST needs to expand its horizon to other developers and stakeholders to ensure they deliver what is best for the developers and project but, in order to achieve this, ST needs to understand the telescopes and their use cases better to provide a good experience.

This is needed as ST is constantly evolving as a new team due to the new hires so needs to align to see the bigger picture. This will allow ST to get into system-level integration testing while increasing general knowledge of the team.

Show
System Team (ST) is working closely with Tango Developers for some time and now ST needs to expand its horizon to other developers and stakeholders to ensure they deliver what is best for the developers and project but, in order to achieve this, ST needs to understand the telescopes and their use cases better to provide a good experience. This is needed as ST is constantly evolving as a new team due to the new hires so needs to align to see the bigger picture. This will allow ST to get into system-level integration testing while increasing general knowledge of the team.
Acceptance criteria:
Hide

Follow a day of a stakeholder when they are testing/verifying/integrating the system

TBD before PI starts: Talk with the stakeholders and come up with a draft plan to address their pain points

Implement the plan

Get feedback

Rollout lessons learned (needs to be identified in PI planning) to the wider audience
Show
Follow a day of a stakeholder when they are testing/verifying/integrating the system TBD before PI starts: Talk with the stakeholders and come up with a draft plan to address their pain points Implement the plan Get feedback Rollout lessons learned (needs to be identified in PI planning) to the wider audience
Expect Dependencies:

Inter Program
Feature Points:
2
Initial Size:
2
WSJF:
0
Story Point Burn-up:
Overdue:

Requirement Status:

PI24 - UNCOVERED
Labels_MIRO:
Team_SYSTEM

Description

This is suggested by d-carlo.matteo and will be updated in detail close to the PI boundary.

This feature proposes a joint collaboration with one of the high level (outside of subsystems) stakeholders (such as Adam but anyone with a Science/Operator perspective) so that we can understand how the telescope and systems needs to be used/tested/integrated to

understand the telescopes
align our assumptions of how with the reality
sufficiently be able to support system level integration testing
improve team knowledge

This feature needs buy-in and some detailed Acceptance Criteria with one or more stakeholders before it can be picked up

Discussion from the Feature Dev Meeting on 6/8/24:

Bruno: I'd like other teams to tell us what they want to see implemented instead of us trying to lead the effort with one or two teams so that we can see what their goals are and what they want to achieve

Meeting Minutes w/ Stakeholders 8/8/24:

Mark:

CI/CD for Data Processing Pipelines
Does not need to be on the images to begin with

UX Expert coming along next PI so we might need to reach them

Building components for data processing pipeline
Getting data into pipelines for test
How to run a notebook against the system mid or low
how to test OSO integration environment

Attachments

Structure

Activity

People

Assignee:: Mort, Ben

Reporter:: Yilmaz, Ugur

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (0%)

Feature Estimate: 2.0

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

Dates

Created:: 06/Aug/24 7:51 AM

Updated:: 02/Sep/24 9:21 AM

Due Sprint Date:: 10/Dec/24

Align System Team with Telescope Stakeholders