Sprint Retro Results & Summaries - OCM Team

jinghualicgi commented 2 years ago

Goal:

Summary of OCM Retro results
Agreed actions will be follow-up afterward

OCM Retro Board: https://app.mural.co/t/leadingsafetrainingtemplate5894/m/leadingsafetrainingtemplate5894/1635367606652/b4fa80bd3eb12b6124583c1b7ab4d3260cf51019?sender=ud8c29093473b548514da7248

jinghualicgi commented 2 years ago

OCM Retro Feb17

Action Points:

[ ] Add effort estimates and due date on each OCM ticket (where is applicable)
[ ] Daily Standup only discuss obstacles, no task/ticket status update
[ ] OCM join BA meeting, ask BA which touchpoint is good for OCM team
[ ] Assign a task/ticket lead when multiple people are working on the same task
- Add Task Lead in the ticket description??
[ ] Get feedback from Users for User Guide
[ ] Meeting to discuss google drive usage and organization: with OCM team and other teams.
- Trish will setup a run through meeting. i.e: OS doc from Suzanne
[ ] OCM team member join Entities/Relationship/Assets Planning meeting
[ ] Ensuring we have operational and implementation processes defined and documented before go live
[ ] Staff's involvement in process guide creation, this can help to get buy in from staff from the beginning
[ ] PI12 require lots of coordination within OCM, try to follow agile - self-organizing led teams to sort out work

jinghualicgi commented 2 years ago

OCM Retro March17

https://app.mural.co/t/leadingsafetrainingtemplate5894/m/leadingsafetrainingtemplate5894/1635367606652/b4fa80bd3eb12b6124583c1b7ab4d3260cf51019?sender=ud8c29093473b548514da7248

Action Points:

[ ] Stop sending issues into the engagement mailbox
- TBC: Maribeth is working with Cameron on an escalation document
[ ] Help OCM team to better understand future system
- Home team's BA to support legacy system (send question to Home Team's BA email )
- BA to understand new systems
- OCM raise request if they need help
- Create/Grant test ID for trying new functions, OCM can setup TEST account to try new systems (Asking BA for help if needed)
- Contact Trish if any blockers
[ ] ZH Tickets Priorities
- ZH tickets order reflect priority
- Due date on each ticket
[ ] KT with Sienna
- Documentation from Sienna (Release Comms)
- Maribeth meet Sienna
- Adding all links/documents under ZH tickets
[ ] OCM need to be informed with release timeline change - April20: Still need actions
- PO update release timeline change in RC channel (Raise this in PO Syc, asking PO)
- Adjust our expectations for big release, i.e SP/GP
[ ] Staff Zenhub Board - April20: will follow-up later
- An OCM ticket has been created, Trish will work with Olisa and Cameron
[ ] Adopt to an MVP focus when drafting communications, guides and etc (We will continue to iterate)
- Ensure all key messages/documents is drafted as MVP, use less time on 1st draft
- Bring this in our next planning meeting, let team to keep this in mind
[ ] Provide more time for preparation for each tasks/communication
- Each change stream should plan well in advance, at least one month in advance for detail task, ideally more longer
[ ] OCM join BA guild April20: OCM cannot find enough value to join BA guild
[ ] Who will demo in Info Session?
- Trish will check with Cameron is he can do the Demo
- Trish bring this to PO syc asking Patrick Heath to be a candidate if Cameron don't have time
[ ] Check Distribution List (DL) for external communications
- Maribeth check and make sure all OCM members are included in DL list
Prepare a weekly update for OCM staff
- Maribeth can collect and prepare/send update
- All OCM change lead contribute to OCM Change checkpoint
[x] Apart from Scrum ceremonies, Setup OCM weekly Team meeting
- OCM weekly Huddle has setup
[ ] Ticket creators write detail ticket descriptions with: 1) Expectations; 2) What need to happen; 3) Who need to be involved and etc. (Like Trish does)
- Trish will consider to create a template

jinghualicgi commented 2 years ago

OCM Retro April20

https://app.mural.co/t/leadingsafetrainingtemplate5894/m/leadingsafetrainingtemplate5894/1635367606652/b4fa80bd3eb12b6124583c1b7ab4d3260cf51019?sender=ud8c29093473b548514da7248

Action Points:

Need follow-up from previous retro

[ ] OCM need to be informed with release timeline change - April20: Still need actions
- PO update release timeline change in RC channel (Raise this in PO Syc, asking PO)
- Adjust our expectations for big release, i.e SP/GP
[ ] Staff Zenhub Board - April20: will follow-up later
- An OCM ticket has been created, Trish will work with Olisa and Cameron
[ ] Ticket creators write detail ticket descriptions with: 1) Expectations; 2) What need to happen; 3) Who need to be involved and etc. (Like Trish does)
- Trish will consider to create a template

Action Points

[ ] Many major releases all within Jun/Jul - needs to be communicated together
- 1. Ask PO when is releases' most realistic date - can we have two months notice to client? - PO Syc
- 1. Communication plan is up-to-date, review in Huddle
- 1. Combined all communication notes to all external users
- 1. Evaluate DL no overlapped
[ ] Knowledge transfer - many leaving and not enough time to learn from them
- 1. Identify current blockers and meeting key resources
- 1. More structured approach: i.e review Suzann's document first
[ ] Touch points with POs, to get updates on releases
- 1. Sprint Review is not enough
- 1. Weekly touch point meeting, PO cannot join - Review our weekly touch point to make it more efficiently
- 1. Bring to PO Syc meeting and discuss

jinghualicgi commented 2 years ago

Action Points:

Need follow-up from previous retro

[x] OCM need to be informed with release timeline change - June09: Still don't know API release timelines: Search+ SP/GP - Fareen will join PO Syc
- PO update release timeline change in RC channel (Raise this in PO Syc, asking PO)
- Adjust our expectations for big release, i.e SP/GP
[x] Staff Zenhub Board - June09: from Megan all staff have GH accounts
- An OCM ticket has been created, Trish will work with Olisa and Cameron
[ ] On-hold: Ticket creators write detail ticket descriptions with: 1) Expectations; 2) What need to happen; 3) Who need to be involved and etc. (Like Trish does)
- Trish will consider to create a template Onhold, will have time after major releases
[ ] Many major releases all within Jun/Jul - needs to be communicated together
- 1. Ask PO when is releases' most realistic date - can we have two months notice to client? - PO Syc
- 1. Communication plan is up-to-date, review in Huddle
- 1. Combined all communication notes to all external users
- 1. Evaluate DL no overlapped
- 1. Keep weekly notice email
- 1. Add coming soon to trigger customer to create accounts (->Ask in OCM Scrum June14th)
[x] Touch points with POs, to get updates on releases
- 1. Sprint Review is not enough
- 1. Weekly touch point meeting, PO cannot join - Review our weekly touch point to make it more efficiently
- 1. Bring to PO Syc meeting and discuss
[ ] Kaine suggested to do a retro for Business Search info document/Collecting Feedback via Feedback form

New proposed Actions

[x] Clarify roles of new BAs and OCM - external partners
1. to include BA and OCM in right meetings
1. Pre-define who should join SBC meeting
1. Define meeting agenda / MoM
[x] All: Review all meeting invites and participants, make sure all right people join different meetings
[ ] Info center(Google Site) is becoming single source with links to google doc (Knowledge base) and OneNote
1. Get staff/biz's input for info center
1. Current status: still using OneNote at this moment (June09: Mags will create a ticket assign to Jinghua)

jinghualicgi commented 2 years ago

@Maribeth-Wilson This is the retro ticket for tracking AP, see if you want to reuse this or want to create a new one.

Maribeth-Wilson commented 1 year ago

Moving this issue to closed, notes have been recorded in my OneNote

bcgov / entity