Sprint Retro Results & Summaries – Relationships

[WaldemarSchneider86]

Goal:

1. Summary of all Retro results for Team “Relationships” in this Epic
2. Agreed Actions will be created as “tasks” (new issue) - to make them visible in ZenHub, to get them done and discuss the outcomes/ results in the next Retro

This Epic includes team discussion about A. What went well (stay here) B. Improvements (stay here) C. Action Items (will be created as a task and linked to this Epic)

[WaldemarSchneider86]

Sprint 19 Retro:

• [x] Loren to follow-up w. Nitin: Business Workflow, Functional description, Feature description
  (Commit to creating documentation for reference purpose)
• [x] SM - All: Commit to review the DoR in Grooming
• [x] SM - Decrease Ad-hoc meetings within & between teams
• [x] SM - SM arrange Demo early: Ask early about Demo: What, who will demo in Sprint Review?!
• [x] All: When Demoing a User Story, open the story and read it with the Acceptance Criteria
• [x] SM: Set-up Team Sprint Review max. 1 h (before Sprint Review w. all) (what is "done"?!)

[lmullane]

I followed up with Nitin and he is well underway wth documenting the workflows, feature descriptions, etc. Will post a link in the RocketChat

[shahriar-khan-fw]

Sprint 20
https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Retro.md Agenda:

• previous Retro action items
• Bug Triage: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Bug%20Triage
• others?

Action items:

• [x] @lmullane to work with BA to Prioritize Bug Column.
• [x] Team will bring in 25% Bugs & Tech Debt into future sprints. SM @WaldemarSchneider86 to remind team to do this at Sprint planning.
• [x] SMs @WaldemarSchneider86 & @shahriar-khan-fw to work with @lmullane to help with Team Goal Setting (goals for next few sprints/ releases were not clear; provide more forecast)
• [x] @pksumesh to send @lmullane API docs to pass to the Assets team.

[WaldemarSchneider86]

re Bugs & Tech Debt - I did update this document, to make sure we will not forget: https://github.com/bcgov/entity/edit/master/docs/Way%20of%20Working/Sprint%20Planning.md

[lmullane]

@shahriar-khan-fw What was the team goal setting action item about again?

[WaldemarSchneider86]

Sprint 21 - summary:

• Bug Template updated: All agreed to use this bug template
• Bug Triage process updated: All agreed to follow
• "hard to split a Feature into tasks" as a feature was to complex
• "Ready for QA" column - John idea to change understanding of this column
• [x] W schedule a workshop w. John, Andrew & Saravan, Thor, Katie or Kial, Roland, Justin or Walter asap, 1hr (agreed w. John; he will think about it and let me know if I can help him or not, Jan 22)

[WaldemarSchneider86]

Sprint 22 A) Positive/ GREAT/ KUDOS:

• Process Flow helps the team to see the flow of a user in the applications, continue to visualize the flow!
• Planning of stories with AC is better now
• Agreed to use the bug template
• Increased transparency processes within teams/ across teams
• Use of Release Label helps Change Management activities
• clarity for partners (navigation, authentication)
• Amit and Nitin organized, initiative, thoughtful
• understand some partner authorizations and business
• team collaboration

B) IMPROVEMENTS

• Maintenance process need cross team
• we need more QA time in TEST Env. (DEV to TEST only on Jan. 30; only a few hrs for Nitin in TEST!)
• Release Process: notify Trish when we release successfully
• As a PO I need more time to Prep for Grooming
• Bug Triage: How agile are we/ how efficient, when we discuss the same bug 2-3 times before (fixing it)
• A process to share feedback's from meetings someone attended (RocketChat, and or Daily)
• more time for our Grooming meeting (solution designing is usually part of Grooming)
• Switch Accounts supposed to be two Sprints, but changed during Sprint to make it in one only
• Distractions and noise (not our team) - more focused time
• Bring Dependency work in our daily stand-up
• meeting outcomes - less sidebars, keep time-box or schedule appropriate time
• combine process flow with UX design
• more issues/ tickets in buffer (in case we run out of issues)
• user stories are coupled and makes it hard to split tasks
• need focus on supporting staff
• more engagement with staff?!?

---

Action items:

• [x] Walde set-up a 30 min Workshop w. Roland, Thor, John and Patrick Wei to talk about Environments a) How do we define Staging, and what is the purpose for Staging? b) DEV - to TEST: When? (and what are the criteria to move to TEST) c) John - Is John the only one to decide re TEST? (risk!?) https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/CI-CD_Flow-Process.md
• [x] Amit - work with Jeremy - before Amit´s holiday re Process Flow
• [ ] Loren: consider 2 Epics for the Sprint Planning, so that dev team has more variety of US´s
• [x] Walde: Maintenance/ Operations: Clarify Operations Process a) Workshop with Patrick, Kial and Richard - to propose a process b) Include Loren and Kaine to validate and clarify process https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Operations-Processes.md
• [x] Loren & Walde: Reduce noise in our team room
• [x] Daily: Inform team members what you learned in team meetings (yesterday)
• [x] Walde: More time for Grooming - extend time box
• [x] Walde: Move Retro to next day, before Sprint Planning - so that team has more time --- Loren updated the invite "Sprint Planning" on Wed bi-weekly - starting with Retro at 9am
• [x] notify Trish when we release successfully --- created template to use for each team; included CM communication in the end: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Release_steps

[WaldemarSchneider86]

Sprint 23:

• We did follow-up on the action items from last retro - and used the Retro Mountain

• Team agreed to follow CI CD steps: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/CI-CD_Flow-Process.md

• [ ] Walde: follow-up on this in next Retro again

• [ ] Walde: Schedule a session this Sprint to define "Release Steps Relationships Team"– based on: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Release-Steps_Entity.md https://github.com/bcgov/entity/issues/2165

• All: Design/ Architecture/ Technical – Workshop: Ad-hoc, whenever the team needs it – let the SM know to schedule it for you

• All: Agreed to keep current cadence and times

• [ ] Walde: Get ducks from Pop - today, Feb 19 he has no ducks available, he ordered them.

• Staging: Developer: Verify by Developer, Developer: Create PR to Master

• Move to “Ready for QA”: Deployed to TEST - Steps here: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/CI-CD_Flow-Process.md

[WaldemarSchneider86]

Sprint 24:

• Retro Mountain - review our improvement items - and in this Epic

1. Liked:

   • New set-up with staging/ test and QA efforts
   • Ensuring DESIGN tickets are pre-fixed with "UI-DESIGN"
   • More time for testing was available: Tickets put in TEST (Ready for QA) early - things into TEST quicker
   • self-organizing team
   • design discussions around VON, auth alternatives
   • Saravan & Sumesh for constantly looking into the bugs
   • Andrew´s efforts to reset the DB for TEST to make it stable for testing
   • support from team members
   • approach of KeyCloak with different teams
   • process change for tracking staff bugs (using label "client/ staff feedback")

2. Learned

   • Load a Sprint 80% (and leave some slack time)
   • Release label for each ticket
   • user feedback on BCSC and account types
   • more clarity on product design/ vision
   • common components, shared architecture
   • GitHub Actions
   • common components are something we have to be very careful about

3. Lacked

   • meetings without an outcome existed
   • scope changes without time to plan, design and engage
   • better allocation/ planning on operational/ support team
   • clear cross-team decisions not documented
   • focus in meetings
   • up-front DESIGN to support development (needed)
   • modifying tickets if the original ticket needs to be updated so that AC is clear
   • involve QA in design discussion
   • time to support other teams larger than expected
   • asks/ requests from other teams were hard to manage/ integrate into the Sprint
   • Coordination on Release Comms
   • EDB Training

Action Items

• [ ] Jeremy: Share decisions w. Trish
• [x] PO: Release on a Thu or Fr?! (so that team can potential fix things after integration)
• [x] Walde: Talk to Richard re EDB Training + involve Loren & Kaine to get EDB Training
• [x] Walde w. Loren re Retro items - how/where to document & track - it´s ok for Loren to keep it here. He want us to follow-up on the Retro items.
• [x] Loren: Release label for each ticket in ZenHub
• [x] ALL: DESIGN item - from a Story in one of the next Sprint(s) - earlier into Sprint Backlog so that it can be done before we groom that story for the upcoming Sprint(s).

Ideas

• Discuss: Sprint status - Mo, 2020-03-02 - morning the day before Sprint end.

[WaldemarSchneider86]

EDB – Notes and Summary

1. What Training EDB Admin
2. Number of people 6-8
3. Who a. Patrick Wei b. Richard Armitage c. Bob Bowles d. Thor Wolpert e. Walter Moar? f. David Roberts? g. Will Kwan? h. ?

 Richard provide more details to Waldemar  Luke will chat with Todd  Luke will get back to me this afternoon  Richard - and or Luke? - reach out to Ian Bott to request training Luke - contract adjustment?  Summarize all, and then send to Kaine Sparks  Kaine wills end Email to Ian Botts

Questions for Luke: 1) Is EDB Training included in the existing contract? 2) Where is the EDB contract stored/ what is the link?

Info from Luke:

• Procured a year ago
• One year ago, the cluster was smaller, less service
• Contract needs to be modified o We need to increase the subscription

Hi Kaine, here the summary/ overview – for you as leader/ director – to follow-up with Ian B. – to get EDB Training. Plan A: Get training (asap) via Ian B.

• Patrick Wei mentioned he needs “EDB Admin”
• It looks like EDB Training is not included in the existing contract (only licences)

Plan B: Contract adjustment – Luke mentioned (and Olena confirmed) that olena.mitovska is working on the renewal/ adjustment of the EDB contract. Potentially training could be included (harder path than plan a).

[WaldemarSchneider86]

Sprint 25:

• Review items last time Retro: https://funretro.io/publicboard/kkoeeqAxMbPg3y2j74U3HiNgIR33/42202cd0-597e-4392-8a91-eb37a5deb129

---

Action Items

• [x] Walde: Try Google Meet to use for collaboration remotely -- talked to Shahriar, he uses the Gsuite from FW that they can use as FW employee - talked to Nitin, and Nitin is able to host GoogleMeet session. Walde is able to particpate only, not to host a session (W has WebEx and Skype for Business).
• [ ] Walde: Workshop w. team: Fr. March 27 - 10-3: remote - (Waldemar set-up): Visualize the Epics from PIP2 - go trough the Epics with the team; identify features for each Epic
• [x] Amit w. Walde: Agree on process re dependency and work that is needed - then chat with Loren -- Create ticket – label it with the appropriate team (e.g. “Relationships”) & “Dependency”– assign to Amit; do not go straight to a team member; bring dependency up in the Daily, ... -- we updated the dependency process to reflect that a dependency ticket has to be socialized with PO: https://github.com/bcgov/entity/blob/master/docs/Way%20of%20Working/Dependency-Process.md

--- idea to discuss about: Move to TEST

• Proposed idea (frequency and time): Every day at 12 we move items to TEST
• Then: No decisions needed and reduce time to coordinate

[ghost]

Sprint 26: Relationships team

Action items:

@lmullane - Loren to clarify Relationships accountability for UX consistency across teams.

@saravankumarpa @saravanpa-aot - UI/UX Review of the screens from Jeremy and Claire needs to be a part of Acceptance criteria. Tasks should only be moved to QA only after UX Approval if there is a UI piece involved. Create UX assurance column in Zenhub

[ghost]

Sprint 27 retro:

[ghost]

Sprint 28 retro-

[ghost]

Sprint 29 retro -

[ghost]

Sprint 30 retro

[ghost]

Sprint 31 retro-

[ghost]

Sprint 33 retro-

[jdyck-fw]

[jdyck-fw]

[jdyck-fw]

Sprint 36

Action items:

• [x] @jdyck-fw - At planning, split out our grouping of bugs/tech debt (10% bugs / 15% td)
• [x] @amit4610 - Ensure that we plan for and document artifacts as a result of meetings
• [x] @Milan-Freshworks - Watch for items at sprint planning that could benefit from more information for QA

[jdyck-fw]

Sprint 37

Action items:

• [x] @lmullane - Practice breaking tickets down further when there are lots of AC
• [x] @jeznorth - Revisit our templates and checklists and ensure we are using them as intended and any required updates on them are made

[jdyck-fw]

Action items

• [ ] @saravanpa-aot - Create a tech debt ticket to cover older UIs
• [ ] @saravanpa-aot - In addition to the AC, include notes around other required work such as API. Capture grooming discussion take-away on a ticket in comments
• [ ] @lmullane - Ensure that agreements and expectations are aligned in supporting other teams
• [ ] @Milan-Freshworks - In grooming, ask "will this be feature flagged?" and then we can track this in the ticket

[mstanton1]

• [ ] @loren - PI Planning. To be mindful of balancing major features.
• [ ] @patrick.wei - Reach out to Jyoti about using tech review to demo load tester.
• [ ] @amit4610 - Post link in Rocketchat for holiday calendar. @all to update by Friday.

[mstanton1]

• [ ] @mstanton1 - Coordinate meeting with other team to discuss staff feature list. Start by booking a meeting with Trish and our team.
• [x] @mstanton1- Book a meeting for our team to discuss the testing strategy early Thurs. Include Loren, Sumesh, Saravan and Milan.

[mstanton1]

• [ ] @rkim13103 @jeznorth to invite team members to design sessions Thursday at stand-up as needed.
• [ ] @lmullane to comment in ticket and reach out to devs when design changes are expected.
• [ ] @rkim13103 @jeznorth to update designs if changes are made.
• [ ] @mstanton1 to ensure items are re-groomed when design changes are made.
• [ ] @saravanpa-aot to raise with devs when larger testing effort is being expended and create extra tickets as needed.

[mstanton1]

• [ ] @saravanpa-aot to ensure devs add estimate for unit tests into story estimate during grooming.
• [ ] @mstanton1 to ensure all necessary documents are attached to ticket in pre-grooming. Confirm in grooming if anything is missing.
• [ ] @lmullane to consider methods to make documents more easily accessible to all team members.

[mstanton1]

• [ ] @Milan-Freshworks to set up 3 scripts for BCSC in Cypress.
• [ ] @mstanton1 @trishreimer to work with team to order OCM tagged items each Sprint.
• [ ] @amit4610 @mstanton1 to create and vet refund tickets (1 ticket Wednesday - Wednesday).

[mstanton1]

• [ ] @lmullane to follow up with team after PayBC discussion.
• [ ] @sumesh-aot to create ticket for scan when we do not receive a successful payment in X timeframe - or for reporting based on Sentry that will help identify payment failures.

[jyoti3286]

Sprint 49 Action items from Retro @rkim13103 - To invite devs for the weekly Thursday Meeting @jyoti3286 - To capture the decision and follow-up action items on the ticket. If required, provide a summary of changes(but not for every ticket).

[mstanton1]

Sprint 50 Action Items from Retro @jyoti3286 to schedule a broader planning session to look into scope. BA's to establish approach for documenting in GitHub with higher level analysis and decisions for features. Schedule a fun/games meeting where we can talk about non-work related meeting

[mstanton1]

Sprint 51 Continue with ongoing action items. @amit4610 has created Zenhub 6900 to obtain 5 test IDIRS. @mstanton1 has created Zenhub 6907 for documentation in Github and has added this to the grooming list.

[mstanton1]

Sprint 52 Continue with ongoing action items. @amit4610 has created Zenhub 6900 to obtain 5 test IDIRS. @mstanton1 has created Zenhub 6907 for documentation in Github and has added this to the grooming list.

AND

@jyoti3286 @amit4610 @mstanton1 to figure out plan for generating requirements on what FAS system must do. Documentation should be made available to Dev's while IP for feedback. @rkim13103 to complete UX assurance against design. No requirement to look at code. TEAM to be cautious of commitment for next PI Planning

[mstanton1]

Sprint 52 Continue with ongoing action items. @mstanton1 has created Zenhub 6907 which is in Sprint 54. Team to be cautious of commitment for next PI planning. @amit4610 @mstanton1 to produce requirements on what system must do an make available for devs while IP for feedback (to be captured in location created by 6907)

Sprint 53 NEW @mstanton1 to create a ticket for grooming for dev work for partner onboarding. @saravanpa-aot to set up a meeting for the dev team to review approach for development work after each sprint planning. @mstanton1 to create a ticket for documenting keycloack groups and access.

[mstanton1]

Sprint 53 Continue with ongoing action items. BA's: Requirements on what system must do. To make available to devs as IP for feedback.

Sprint 54 NEW @rkim13103 to update wording in tickets when changes are agreed upon @here - review wording for completeness during grooming @SateeshFW - to create release ticket each sprint. Team to review bugs as they can't be feature flagged.

[SateeshFW]

Sprint 54 Continue with ongoing action items. @SateeshFW - to create release ticket each sprint. Team to review bugs as they can't be feature flagged.

Sprint 9.2 New @all - Allocate some time in Sprint for QA @Dev - Validate the designs done by Roy @all - any MVP solution, please hightlight it to BA/DEV/UX

[SateeshFW]

Sprint 9.2 Continue with ongoing action items

Sprint 9.3 New @Jyoti - PO Sync meeting book 15mins to go thru the BA tickets which have dependency @devs - Tag the tickets to Melissa or Jyoti or Amit for testing. @sateesh - Check the tickets if it required UX assurance @Jyoti - Another meeting with small set of team for the documentation on the EJV flow

[SateeshFW]

Sprint 9.3 continue with ongoing action items...

Sprint 9.4 New @all - Lets consider 5 bugs for the next sprint. @jyoti - to check with Carol for solution to design the tickets @sateesh - Forward the invite to all for pre-grooming and share ticket details rocket chat @Jyoti - Talk to Yvnne for any dependencies on home team

[SateeshFW]

Sprint 9.4 continue with ongoing action items...

Sprint 9.5 New @rarya-freshworks - Focus first on the application user interface testing rather than db or api testing @Devs - Focus on the quality of the application rather than the finishing the tickets faster @amit4610 - Create FAS document for making the requirements easy to understand

[SateeshFW]

Sprint 9.5 continue with ongoing action items...

Sprint 9.6 New @jyoti3286 - Recommended the PO group to move the Stakeholder Review meeting to Wednesday. If this works, then we can have internal demo on Tuesday (last day of sprint) for around 15 mins and prepare well for the demo. @jyoti3286 - Create smaller user stories (not more than 8 points) so that they can be completed quickly. @rkim13103 - Finalize/freeze the designs before the start of the sprint.

[SateeshFW]

Sprint 9.6 continue with ongoing action items...

Sprint 10.1 New @SateeshFW - Work on Release planning considering the scope, regression testing completion. @rarya-freshworks - Target to demo the FAS e2e automation in the next sprint demo, at least internally to the team and later to the stakeholders @SateeshFW - Setup meeting with QAs and POs to discuss on the QA related priority items @ba - Documenting on FAS based on the template we have currently

[SateeshFW]

Sprint 10.1 continue with ongoing action items...

Sprint 10.2 New @rarya-freshworks - Work on the FAS automation and also start working on the backend API. The high priority will be for the FAS automation @team - Create small stories and Epics for the Pay-API requirement. Need to discuss on these stories in the next grooming

[SateeshFW]

Sprint 10.2 continue with ongoing action items...

Sprint 10.3 New @Jyoti - Will discuss in PO Sync on the release plan coordination between teams. @Sateesh - To follow the release process for the relationship team @ All - The combined efforts to take a ticket to the done column should be considered for the estimation @ BA - The Ops tickets should be discussed in the BA Guild and then a decision can be taken on that ticket before passing any ticket to Dev.

[ba]

Could you please stop tagging me? :)

On August 25, 2021, GitHub @.***> wrote:

  Sprint 10.2 continue with ongoing action items...

Sprint 10.3 New @jyoti https://github.com/jyoti - Will discuss in PO Sync on the release plan coordination between teams. @sateesh https://github.com/sateesh - To follow the release process for the relationship team @ALL https://github.com/ALL - The combined efforts to take a ticket to the done column should be considered for the estimation @ba https://github.com/ba - The Ops tickets should be discussed in the BA Guild and then a decision can be taken on that ticket before passing any ticket to Dev. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bcgov/entity/issues/2125#issuecomment-904992199, or unsubscribe https://github.com/notifications/unsubscribe- auth/AAASJYAPGHASXS2QCFVCEBTT6QF4LANCNFSM4J2GOFCQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification- email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification- email.

[SateeshFW]

Action items from Sprint 10.3 continues

Sprint 10.4 New @rarya-freshworks - Focus more on the FAS functionality testing for bug free delivery. Add details, in each ticket, of the scenario followed for the testing @SateeshFW - Setup a bug bash meeting (~30mins) to do the testing of the FAS functionality by the complete team @SateeshFW - Work with Jyoti to create new tickets for any changes done in the ACs of the tickets. This will help in tracking the changes using new tickets rather than updating the existing ACs

[SateeshFW]

Action items from Sprint 10.4 continues

Sprint 10.5 New @SateeshFW - Discuss with Rai on any challenges in the manual testing or test automation @SateeshFW - Discuss with Sumesh on the process to record the efforts spent in supporting partners

[SateeshFW]

Miro Retro Board - https://miro.com/app/board/o9J_kqJbIfY=/?moveToWidget=3074457365092585472&cot=14

Action items from Sprint 10.5 continues

Sprint 10.6 New @rarya-freshworks - Check with Other team members on the Keycloak integration in Automation @rarya-freshworks - Add the scenarios as AC in the tickets, if required @SateeshFW - Include the area from the Agile maturity assessment board into the Miro Mountain board

[SateeshFW]

Miro Retro Board - https://miro.com/app/board/o9J_kqJbIfY=/?moveToWidget=3074457365935653633&cot=14

Action items from Sprint 10.6 continues

Sprint 11.1 New @SateeshFW - After Sprint planning, spend some time with the team discussing the sprint goal in detail. @SateeshFW - In the planning meeting, discuss with the team the average velocity and finalize the capacity of the sprint considering the vacation in the coming weeks. @SateeshFW - Include the area from the Agile maturity assessment board into the Miro Mountain board for the next retro meeting @jyoti3286 - Ops tickets should be discussed with Kaine on the strategy to execute the Opts ticket. Need to discuss in the PO Sync. @jyoti3286 - Discuss with POs in the PO Sync meeting on the guideline to finalize the completion % of tasks in the sprint for all the teams. @SateeshFW - Maintain an xls sheet with all the demo items recorded in it.

[SateeshFW]

Miro Retro Board - https://miro.com/app/board/o9J_kqJbIfY=/?moveToWidget=3074457366780383725&cot=14

Action items from Sprint 11.1 continues

Action items from Sprint 11.2 Retro @SateeshFW - Schedule a date for the team (Wed would be preferred) for 1hr for each sprint for a tech demo| @SateeshFW - Plan for the internal demo on the last Friday of the sprint. @jyoti3286 - Add P1 bugs in every sprint planning @sumesh-aot - Improve onboarding document. For notification API, need to create a Spec., @SateeshFW - Create a ticket for the next sprint @pwei1018 - Deploy the ticket 9686 to prod in the next release.

[SateeshFW]

Miro Retro Board - https://miro.com/app/board/o9J_kqJbIfY=/?moveToWidget=3074457367678640523&cot=14

Action items from Sprint 11.2 continues

Action items from Sprint 11.3 Retro @SateeshFW - Create a Doc in Github where the team can add the topic required for KT from Sumesh.  Discuss also in the demo sessions every week and share the meeting details with all the Registry ppl. @rarya-freshworks - Run the test daily and check the results/files every day. @SateeshFW - Keep UAT as part of the agenda for discussion in standup. @jyoti3286 - Include the Techdebt, Documentation, P1 bugs tickets in the Planning. @jyoti3286 - Work with John on offloading the work from him.