MEETING RECORDING:

https://zoom.us/rec/share/Xkt5Ti5qZ2mOVI-5uLV658k5bGzM_-DjYi4lGjocmb3Q7VgGaR_77BV3kqeNk48.fV3OWIsNQ4o7Y6VB Passcode: eUY%K9l5

Meeting Summary by Nehar Sultana :

10th Nov. 2023

• Meeting agenda walkthrough
  • meeting kickoff
  • reviewing phase 2 deliverable
    • handoff discussion
    • checking the project charter
  • PM methodology exercise review
  • PM readiness check
• New learning can be unlearning
• The reason behind the processes and meeting cadences is so that the team is aware of who is doing what and when
• As a liaison, what are the most impactful things to bring back to the team?
  • Are the other teams’ work aligned with the charter and deliverables?
  • There is still trouble in defining the user group at this stage
    • Working in agile also means working with unknowns
  • Is the progress aligning with the client’s demands?
  • Are there any capacity issues?
  • Scalability of the progress: can we meet the client’s demand within this project?
  • The client is open to the team’s findings and the direction of the project
    • But we have to wait for the client’s green signal before we can make any changes from the original goal
• Project charter
  • Are the teams following those set goals?
  • Working in agile also means working with unknowns
  • How to work in scalability
• Benefits of having redundant info generated from liaisoning and lead meetings
  • Joanne
    • It is better if the same message is communicated across the workstreams
    • Are things aligning well?
    • Helps in high-level viewing of the project roadmap
    • Aligning the progress with the Kanban board
    • How to manage in case of conflicting deadline(s)?
  • Brenda
    • Redundancy helps in confirming things
    • Helps find the gaps
• Miller’s take on the project's progress
  • The whole project is in agile mode; therefore, changes are happening and things are being added
  • After today’s demo, we’ll get to see some increment
• Diverge to converge due to the exploration in different areas
• The design team will kick off after the 3rd sprint
• Handoff discussion
  • It is a condensed documentation containing
    • Project goal
    • knowledge during stakeholder meetings
    • communication enclosure to ensure some transition
    • Steps for the next stage/team
    • Reflections and recommendations
    • Gaps and challenges
  • Brenda walks through the handoff of another project, “Safe Place International”, as an example
  • Tech Fleet has already provided a template
  • We can develop one from scratch given the necessity; Amp up did it
  • Handoffs include reflections and recommendations for the next team
  • Cannot be broad
  • Has to make sense for the recipient
• UXR and Product Strat teams were confused regarding the client's demands
  • The liaison is the PM’s voice
  • Check the Project charter and roadmap for updated and clear info
  • Check the resources from the notion page
• Project charter walkthrough
  • It’s duplicated on the all-team Figjam
    • PM team has a separate one
  • It is a high-level roadmap that may change over time
  • How do you interpret the color codes used in the charter for different teams?
  • What has and hasn’t changed since the beginning?
    • Questions raised at the start of the project changes as the project progresses
    • Potential risks tend to stay the same throughout
• Sprint board walkthrough
  • Milestones start to form after sprint 4
  • When should we start filling the board?
    • Kim: 2 weeks before the deadline
    • Joanne: when we have more information than before
    • Nehar: after a couple of UXR interviews
• PM methodology exercise
  • Miller mentions the waterfall and agile method
  • Joanne mentions the widely used but not that heard of PRINCE2 method
  • Kim mentions the **scrum** and lean method
  • Kanban
  • Agile, UX, and You | Tech Fleet
• Meeting during the Thanksgiving week is canceled 🦃🥟