My first attempt at distilling the PM checklist for a feature release process into an infographic (Mobile Apps Context). Would be interested to know from the community what could be added & improvised in the same #productmanagement #product #mobile #mobileapp #mobileappdevelopment #pm #productmanagers #productmanager #mobileapplication #mobileapplicationdevelopment #androidappdevelopment #iosappdevelopment

1. A short story of a feature update
to be released ~3 months from now
Decision Making in the
current context
Fixing Goals
Breaking down the goals
What are the metrics for these customer segments
which will be affected.
KPI1, KPI2, KPI3
Who are the customer segments we are targeting
Spenders/Non-Spenders , New Installs/D7 folks/D28+ folks
Brainstorming
w.r.t fixed goals
Collect as many relevant ideas/hypotheses
as possible without passing judgement
Research
Competitor Analysis, Look Alike/Cross
Pollination research by PM/Design
Secondary Research
Existing Qualitative / Anecdotal evidence
Quantitative Insights from existing data
sources
Primary Research
User Studies/Customer Interviews
Collecting 2 cents
from people on the floor
Inside the team Product Design JAM
QA + Engineering +
Design + Analysts + Community
Cross project individuals/SMEs
interested in providing their 2 cents
Coming up with
Top possible feature designs
For each Feature
Representation
Mapping the user journey
for each customer segment
Impact Estimation of each feature broken
down by phases of customer journey
Rough Engineering estimations
Primary Goals of the feature
Present Top 3 options to
executive
Features Locked for the update
Foundation Phase
Development Phase Begins
Sprint Cycles Pre-release preparation
Limited Release
Post Release War Room
Next Roadmap Item -->
Further decisions based on limited release
performance
Stability Monitoring
Measuring performance of launched feature
for target customers segments (KPIs) as well
as aggregate impact to find adverse effects
on other segments
Optimization of levers associated with feature
/ Experimentation
Community & Review feedback
Contingency Plans
execution if needed
Hot Fix
Switch off Server Controlled Feature if required
Plan for next update in combination with feedback
from current release
Gradual to full roll out in case all goes well
Release date or scope movement
based on progress made.
Rituals
Backlog Grooming
Sub Tasks
T Shirt Sizing
Sprint Planning
Daily Scrum
Mid Sprint Review
Sprint Retrospect & Demo
Sprint 0
Technical Investigations & Research
High level Epics/Stories created at higher level
for the backlog
PM & Design detail out User Acceptance
Criteria for the Stories.Objective is to
minimize change in requirements caused by
PM & Design
Creating Stories for telemetry capture. Ideas
for telemetry sourced from team through a
telemetry JAM apart from PM/Design
research
Situation would have changed from the time
we created the roadmap or from the last quarter
when the the update plan was revised
Iterate on feedback from execs
am
uldotexe