Scrum Master RACI

Responsible (R):

• Updating Team section in the wiki: Roscetti, Nicolas 

• Onboarding and Offboarding team members: Roscetti, Nicolas 

• Improve team performance
  • Core Board with epic Feature, build a roadmap
  • Lesson Learned in the wiki
• Upload Sprint Reports in Wiki
• Cleaned data velocity chart in this doc
• Facilitate Retrospectives and Sprint Planning (partially), miro board

• Coaching the team members in self-management and cross-functionality;

• Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done;

• Causing the removal of impediments to the Scrum Team’s progress; 

• Helping find techniques for effective Product Goal definition and Product Backlog management;

• Helping the Scrum Team understand the need for clear and concise Product Backlog items;

• Helping establish empirical product planning for a complex environment; 

• Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.

• Facilitating stakeholder collaboration as requested or needed.

• Leading, training, and coaching the organization in its Scrum adoption;

• Planning and advising Scrum implementations within the organization;

• Helping employees and stakeholders understand and enact an empirical approach for complex work; and,

• Removing barriers between stakeholders and Scrum Teams.

Accountable (A):

• Establishing Scrum as defined in the Scrum Guide
• Ensuring everyone understands Scrum theory and practice, both within the Scrum Team and the organization.
• Scrum Team’s effectiveness
• Enabling the Scrum Team to improve its practices, within the Scrum framework.

Consulted (C):

• Collaboration with cross-functional teams, including researchers, scientists, developers, and product managers/owners
• for Requirement Analysis – Technical, Impact Analysis (High Level Estimations), Define Product Backlog, Prioritize Product Backlog, Create User Stories and System/QA Testing

Informed (I):

• Requirement Analysis – Business, Testing Process and Build Management.

Miro link: https://miro.com/app/board/uXjVP3CeiiY=/

Team RACI

Technical Roles RACI

Purpose/Audience

There is no clear process that must be followed for deploying a new application/solution to GCP.
The Lab Booster team has received different and at times contradicting information from and guidance on this topic from different parties, that has led to delays and confusion.
The process described in this document is intended to provide clarity on the required/correct process. This document is addressed to all members of Lab Booster projects as they should be aware of the process and may be called upon to participate in certain stages of the process.

Overview

The process consists of seven (7) high level steps:

1. Product Architect works with Enterprise Architect to align on high level/logical architecture.
2. Product Architect works with Data Architect to align on high level/logical data architecture, e.g. data design, schemas, data flows etc.
3. Product Architect works with EBS (Cloud Ops) team to align on GCP Solution Architecture.
4. Product Architect & Product Manager present Architecture Impact Analysis (AIA) to Architecture Review Board (ARB).
5. Product Architect works with with Platform Architect and EBS team Solutions Architect to align on define detailed technical design, e.g. implementation plan, costs etc.
6. Product Architect works with Security Architect to review security considerations for application/solution and gain approval to initiate implementation.
7. Product Architect submits detailed request to EBS team to start implementation.

Architect roles

Step-by-step guide

Below is a detailed description of the steps mentioned above.

Step 1 - 1 Product Architect + 1 Enterprise Architect

If feedback re:misalignment is provided by the Enterprise Architect, one or more follow-up sessions may be required to gain validation for moving to next phase of the process.

Step 2 - Product Architect + Data Architect

Step 3 - Product Architect + EBS

Step 4 - AIA Presentation

If feedback re:misalignment is provided by the ARB, one or more follow-up sessions with Enterprise Architect and/or Data Architect and/or Cloud Ops team may be required to gain address feedback from ARB, as well as a follow-up presentation to the ARB in order to gain validation for moving to next phase of the process.

Step 5 - Product Architect + Platform Architect

Step 6 - Product Architect + Security Architect

If feedback re:misalignment is provided by the Security Architect, one or more follow-up sessions may be required with Platform Architect (and optionally Cloud Ops Team) to address security concerns in design, followed by a follow-up session with the Security Architect to gain validation for moving to next phase of the process.

Step 7 - Product Architect request submission

Related articles

Definition

The design process helps translate business needs into detailed requirements.
It consists of a few steps that helps the team brainstorm together to ensure we answer our stakeholder needs and maximize the product value.

Design Process

This process is represented for the Data squad in the 2-Data Design board.  

DoD Definition Workshop: https://miro.com/app/board/uXjVPBkF6Yo=/

Agreed DoD:

• Manual Test Cases - Test Report (No automation test)
• Business documentation on the wiki (ask for access)
• Technical documentation
• Delivered in PROD
• No impact on other features
• Acceptable performances
• Test case design
• Test execution report 
• Wiki update
• More elaborated ticket will have less bugs/UI changes
• By default, dev is fully consistent with the mockups

Agreed DoR:

• Stories contain description using INVEST model

• Acceptance Criteria listed
• UI/UX wireframes attached to story (where applicable)
• Story stories estimated to fit into 1 sprint
• External dependencies resolved

The RUN team will be responsible for the following:

• Solve any issues to keep the application running as expected by the users or DT team
• Providing technical support to end-users as needed to resolve their issues.
• Maintain and update the knowledge base or documentation for the complex issues encountered.

Define the process for transitioning components to the support team:

• Once the build is ready to move the component to Production, they raise a request to the RUN team to move them to Production.
• Once the component is moved to Production, the Product Owner will contact the Service Owner to handover the maintenance of the component to the RUN team.
• Schedule KT sessions: The Service Owner will schedule the KT sessions for the BUILD team to share the documentation and provide knowledge transfer to the RUN team.
• The Hyper care period is 30 days after the component is delivered in Production during which the support responsibility is with the BUILD team. It can be reduced to 15 days if the delivered component is simple.
• The support team will assume ownership of the component and provide necessary maintenance and support services post the hyper care period.
• If the component requires further development or enhancements, the support team will coordinate with the build team.

 Define the process for reporting and resolving issues:

• End-users will report any issues or problems to the support team through an established support channel ServiceOne. The user guide to report the issues for different markets are available in the below table:

• The Service Owner will prioritize issues based on severity and impact on business operations
• The reported issue is first investigated by the Service Owner and then assigned to concerned teams based on the component affected. The different teams that are associated with the support of the application are as below –
  • Service Owner team - IS R&I Lab processes – DataLab
  • WebApp team - IT Vanenburg GCP Apps
  • Data team - IT Data & Analytics / IT Data Stellar Talend L3
  • ELN team - IS R&I Lab Processes - ELN L2 (partner)
  • CloudOps team - IT Vanenburg GCP Ops
• The support team will investigate the issues and work to resolve them as quickly as possible. If they need additional information, they reach out to the user directly or the Service Owner.
• If the issue cannot be resolved by the support team, they will escalate it to the build team to assist for further investigation and resolution.
• Update the end-user: Finally, it's important to update the end-user on the progress of their reported issue. This could include providing an estimated timeline for resolving the issue, or letting them know when the issue has been resolved.

DataLab Acess

The details of the datalab access management is described in the following link.

GCP Project - Big Query and Google Cloud Storage

You can request an access to one or several GCP project environement. 

1. Go to Google Groups and in the "All Groups" tab, please search for labbooster.
2. Depending on your function, please request an access on one or several of these groups. Dataviz is about visualisation of the data exposition layer (Data Mart), whereas developers will grant you modification permissions on the datasets and on Data Cloud Storage.
3. In the "reason for joining", please describe:
   1. your function
   2. the GCP BigQuery projects (batteries, coatings, materials) and environments (DEV, TEST, PPROD, PROD) you are interested in 
   3. the tasks you are supposed to perform (create tables, visualize data to check accuracy,...) 
4. The request will be validated by Roscetti, Nicolas and the owner of the group GNANA SEKAR, Prasanth will provide access to the GCP.