ROF: Sprint Retrospectives

Suggest meeting with RSIG team to let us know where they are at, and brainstorm ideas, identify tasks, and discuss timelines. It’s not a business centric-meeting, but a technical meeting.

Maggie

Complete

Write-up a sprint planning agenda:

1. Team to identify personal days off / holidays in upcoming sprint, and add to DevOps sprint. Sprint board > Capacity.

2. Leave tickets unassigned or hybrid

3. Set sprint goal

Maggie

Not Started

Reprioritize testing that we have French translations for all strings

Ashiq, Maggie

Complete

Clean-up and reorganize Confluence development articles

Jugraj

Not Started

Document process for hot-fixes (fix/test in ACC, then fix/test in QA - same story)

Maggie

Not Started

Create and share the page for glossary (doesn’t need to have a full list of acronyms)

Ewa

In Progress

Write a tech investment PBI to clean up the Azure resource groups for DEV

Jugraj

Not Started

Write-up how release testing will go - anything for 1.2 we test in ACC, anything for 1.3 we test in QA

Maggie

Not Started

Health check: write (or update existing) story and reprioritize to verify user permissions in any given environment

Ashiq or Jugraj?

Not Started

Put together a document outlining groups / permissions needed to test ROF (any environment)

Jugraj

Not Started

Set up a meeting with Will to discuss SonarQube setup (will remove the need for local setup)

Ashiq

Not Started

ACC testing: be more thorough about testing specific roles (and in FR)

ROF Team

Complete

• Added to ACC testing tickets for release 1.2.0

Ask Will about the possibility of team being able to block off focused work time

Maggie

Complete

• Spoke with Will, he noted that we can choose as a group which afternoon we would like to schedule for no group meetings (except emergency meetings) and write it in the team charter

• We cannot block the time off in our calendar, but we can make a group note at top of the calendar so our team and RSIG team can see this is our focused time

Let Dave know that we will need the RSIG migration plan when it is ready, and a list of tasks the ROF team needs to complete to support the migration, so we can create tickets and plan our work

Maggie

Complete

• June 7, 2023 - Sent Teams message to Dave outlining our request

• June 8, 2023 - Discussed with Dave and Will during leadership standup. They are aware of our request.

Add ticket to ROF to account for Jugraj’s time helping RSIG team with RSIG migration to cloud

Jugraj

Complete

Discuss with RSIG team the creation of a cloud db dedicated to end-to-end Playwright tests

Jugraj

Complete

• Xu confirmed that we can use a cloud DB, RSIG_Azure. She said the RSIG team needs sometime to get the db ready but she will let us know

Determine sprint goal during sprint planning

Full team

Complete

Outline steps to refresh RSIG db

Maggie

Not started

Remove the following columns from sprint task board: database, development, QA ready (I don’t know if we can remove, as we use the status), and testing

Maggie

Complete

• Talked to Will. He was not sure how to remove the columns.

• Emailed DevOps champions. They are also not sure how to remove the columns, and think it may be part of the default scrum template we are using.

• Marine is using a custom template. It’s possible that we might need to use a custom template.

• As a test, I deleted the state “Database” from PBIs and it was not removed from the taskboard.

• I have also searched online, looking at how-to articles and help forums. I haven’t found an answer, but others seem to have the issue as well.

• Fix: Organization settings - delete task states to remove columns, as the board is the “taskboard” .

Add RSIG DEV environment folder link to Confluence

Maggie

Complete

Create meeting to discuss how we will proceed with QA testing / prod release going forward

Maggie

Complete

• Scheduled meeting for March 17th - QA testing

• Scheduled meeting for March 17th - prod releases

Create bi-weekly release meeting to discuss:

• Sign-off on releasable stories

• Last minute fixes to be added to release

• Features to hide for release (if required)

Maggie

Complete

• Scheduled bi-weekly on Wednesdays starting May 24th

How do we deal with features that require feedback or work to be completed by other teams before we can develop the feature?

We will create two tickets:

Ticket 1: Outlines communication with external team. Once communication is complete, we can close the ticket. Ticket can be brought into the sprint. Effort level should be assigned.

Ticket 2: Create ticket outlining work that needs to be completed after communication / work has been completed by external team. We can bring this ticket into a sprint when we are ready to work on it.

Example:
Ticket 1: Communicate with MAACE team we need endpoint work complete.

Ticket 2: Switch ROF endpoints.

Talk to Steve and Dave sprint review planning and dry run. Team would like:

• Monday - cancel sprint review planning. Team makes a commitment to discuss in Teams chat by end-of-day Monday

• Tuesday - would like to separate RSIG and ROF dry runs

Maggie

Complete

• Messaged Dave and Steve on May 2

• Decision:

  • We will cancel the Monday sprint review planning session, and discuss over Teams.

  • Tuesday sprint review dry-run will be ROF team only.

RSIG knowledge transfer session with ROF. Create meeting for Jugraj, Ashiq and Xu to transfer knowledge.

Jugraj and Ashiq will come up with specific questions to ask Xu in advance of the meeting.

Ashiq

Complete

• Discussed with Jugraj and agreed that Xu’s data dictionary should be sufficient, as we don’t have specific questions.

• Received the data dictionary form Xu (see PBI #263629)

Meeting to discuss creating two testable environments - one for current release and one for future release. Invite Jugraj and Ashiq to attend.

Maggie

Complete

• Created meeting for May 2

• Decision:

  • QA - Future Release

  • ACC - Current Release

Message Norm, and ask if it is possible to have a deployed version of RSIG.

Jugraj

Complete

• Norm on vacation until end of May

• Asked Entai instead, and she said that she can deploy dev

Provide Maggie & Tarek with the ability to switch roles in ROF.

Jugraj

Complete

• Application Developer roles granted for Maggie and Tarek

Add documentation for security groups as part of the definition of done

Maggie

Complete

• Added to the ‘Definition of Done’ on the sprint planning page

Create backlog item to address the following:

• Documentation for security groups

• RSIG user attributes

Team would like the backlog item to be added to sprint 31

Jugraj

Complete

• 263892

Create meeting to discuss testing and cut-off time

Maggie

Complete

• Meeting discussion: Sprint Review - we will only add to the Sprint Review agenda backlog items that have the definition of done complete by end-of-day Monday, otherwise they will not be added to the Sprint Review (e.g. dev, unit test, QA, automated testing, acceptance criteria complete), and is available in QA environment

• Possible to move the sprint planning, retrospective, other meetings to the Tuesday, so we can be ready to go on Wednesday morning.

• Dev and QA can work on documentation, etc. on the Tuesday

• Move the sprint planning to Tuesday - after the review

• Move the retrospective to Wednesday

Create example PBI with tasks

Grace

Complete, Email sent on Wed 2023-04-12 4:55 PM

Research how DevOps is used by external teams

Steve

Not Started

Reach out to Will and ask if he can recommend someone from another team to give us insight into how they use DevOps

Steve

Not Started

Ask Jeff if he wants to continue to attend the sprint planning meeting

Steve

Not Started

Define backlog item definition of done

Maggie and team

In Progress

• Definition of done has been started on the sprint planning page. Need to review with team.

Research MOSCOW and plan a training session

Steve

In Progress

Discuss with Dave and Maggie if we should have a combined RSIG ROF sprint review

Steve

Complete

Request additional columns in WLM analytic dashboard

Jugraj

On Hold?

Review accessibility document and work completed by Francois

Maggie

Not Started

Introduce planning poker tool tool to team

Ashiq

Complete

Investigate ways to improve CI/CD process

Database documentation

Jugraj and Maggie

Discuss table directory

Complete

• Discussed the possibility of creating a table directory in RSIG with Xu on March 5th, and does not recommend adding it to the RSIG db.

• Xu has offered to set up a Confluence page after release 35.

• Jugraj noted that we primarily use XR