-Understand how recurring activities create clarity in an otherwise complicated role -Learn what these recurring meetings look like with real-life examples -Understand how to use each meeting effectively to drive your product forward

1. Meetings in the Life of an Agile PM by
Microsoft Product Leader
productschool.com

2. Your Product Management
Certificate Path
Certificates
Product Manager
Certification™
Senior Product Manager
Certification™
Product Leader
Certification™

3. Corporate Training
Level Up Your Team Management Skills
productschool.com

4. Do you enjoy Product School
events?
We want to hear from you!
Scan the code to fill out this quick questionnaire
so we can provide you with more value.
Questionnaire

5. Free Product Management Resources
Resources
Events Courses Podcasts
Newsletters Communities eBooks and
Reports

6. Meetings in the life of an agile PM
Alana Dickson
Product Manager, MicrosoftViva Insights

7. Alana Dickson
S P E A K E R

8. A G E N D A
2.
1.
Text, content
Text, content
4.
3.
Summary
Text, content

9. What does it really look like to be a PM, day to day?
Presentation centered around six key meetings
Points to note about this presentation:
✔ This is to show a day in the life, to give an idea
of a PM, and to give tips. This is not the only wa
to handle!
This presentation will help with:
1. Give an idea of what it looks like day to day- can be hard to
conceptualize sometimes
2. Give tips for how to get the most out of these meetings
3. An example of how I kept it together- keeping it al One of
the hardest part is staying organized- these meetings &
tips give structures, ways to make sure that you do that

10. THE TWO-WEEK VIEW OF MY MEETING CYCLE
Monday Tuesday Wednesday Thursday Friday
Sprint
kickoff
Stakeholder meeting
Standup Standup Standup Standup
Monday Tuesday Wednesday Thursday Friday
Sprint
Grooming
Stakeholder
meeting
Sprint
Estimation
Sprint Retro
Standup Standup Standup Standup Standup
Points to note about this presentation:
✔ These meetings were my recurring
fundamentals. Many others (roadmap
planning, etc) will occur IRL.
✔ I will use one feature (Peloton high five) as an
example throughout my presentation. I have
never worked on this feature or on Peloton
products!

11. STAKEHOLDER MEETING
Weekly
Business stakeholders,
design lead, tech lead
Here’s the feature. I’d like to hear thoughts on
privacy and alignment with community initiatives.
PM
Need safeguards for users who don’t want to
receive high-fives
Privacy
I’ll show an updated next week based on some
of this feedback, and we will have final
alignment then.
Can we have this feature interact with our
Peloton Together class options?
Head of community
We should time this feature with our Live
Session launch.
Marketing
PM

12. STAKEHOLDER MEETING
This meeting helped me to handle competing stakeholder demands
Tips:
✔ Include all stakeholders together in one meeting
✔ Ensure that all stakeholders routinely attend
✔ Have tech lead in room (their alignment is critical!)
✔ Let stakeholders know about tradeoffs of decisions (i.e. if we prioritize feature X, we have to deprioritize feature Y.)
This meeting is where decisions were made
Tips:
✔ Send pre-reads prior to meeting
✔ Meeting is discussion & decision (not content review)
✔ Send meeting notes that are a source of truth for the group and refer back to them often.

13. SPRINT GROOMING
Once a sprint (every two
weeks)
Tech lead & SMEs
Here’s the user story, requirements, and design
for this feature. What roadblocks do you foresee in
development, and what other information would
the team need in order to be able to develop this?
PM
When a user leaves a class, we don’t refresh the
feed for one minute. How to handle when a
user tries to high-five someone who’s left?
Tech Lead
“My Feed” frontend SME
We’ll talk to that team, and update this feature
accordingly, before estimation.
PM
Being able to high-five is dependent on the
person component being interactive. We’re
dependent on another

14. SPRINT GROOMING
Tips:
✔ Finish editing your user stories or tickets by an agreed upon time so that your tech leads have time to review pre-meeting
✔ Take notes on feedback, dependencies, and changes needed in the ticket to refer back to
✔ Establish general POVon which team member may work on the item

15. SPRINT ESTIMATION
Once a sprint (every two
weeks)
Development team
At a high-level, here are the user stories,
requirements, and design for the high-five
feature.
PM
How many days do you think it would take to
build the high-five feature?
Tech Lead
Development Team
It looks like on average, you think 3 days.
Tech Lead

16. SPRINT ESTIMATION
Tips:
✔ Sit back and relax! You don’t have a say in estimates, but are on-hand to answer any questions

17. SPRINT KICKOFF
Once a sprint (every two
weeks)
Development team
Based on the estimates & the capacity that we
have for the next two weeks, we’ll work on the
high-five feature and Peloton together this sprint.
PM
Alexa, if you have capacity this sprint, you can
work on High Fives.
Tech Lead
Now that everyone knows the goal of this
sprint & what they’re working on, we’ll start
the sprint.
Tech Lead

18. SPRINT KICKOFF
Tips:
✔ Give business context, paint higher-level picture
✔ Give ideas of business impact- show what cool work it’s doing!

19. STANDUP
Daily
Development team
Based on the estimates & the capacity that we
have for the next two weeks, we’ll work on the
high-five feature and Peloton together this sprint.
Development team member
Let’s meet to unblock that later today.
An update from my end is that the high-five
feature is going to be featured on home-page.

20. STANDUP
Tips:
✔ Make thank yous a main part of it
✔ Ask dev to flag if they plan to release features to avoid miscommunication
✔ Devs need to work out dependencies, etc
✔ Opp to alert devs to business conversations, larger shifts happening on regular basis
✔ Take conversations offline so as to not make the standup longer than 15 minutes

21. SPRINT RETRO
Daily
Development team
Based on the estimates & the capacity that we
have for the next two weeks, we’ll work on the
high-five feature and Peloton together this sprint.
Development team member
Let’s meet to unblock that later today.
An update from my end is that the high-five
feature is going to be featured on home-page.

22. SPRINT RETRO
Tips:
✔ Say more here
✔ Add a section for Kudos

23. 2.
1.
S U M M A R Y
Text, content
Text, content

24. Thank You!
WWW.PRODUCTSCHOOL.COM

25. Part-time Product Management
Training Courses
and Corporate Training
productschool.com