1. What is a roadmap ?
   1. "Why" behind "what" you are building ? Plan for your strategy.
   2. - Vision and strategy - Guiding document for executing a strategy - Get stakeholders in alignment. - Facilitate discussions and scenario planning.
2. Why a roadmap ?
   1. Bring everyone on the same page : Executive team, marketing, support, engineering management.
   2. Product vision Product Goals Product road map Release plan and backlog.
      1. Product Vision
         1. - Strategy first approach - Makes easier to articulate product vision. - More clarity on product priorities.
      2. Product Goals
         1. - Competitive differentiation - Customer delight - Technical improvements. - Improve customer satisfaction. - Increase LTV.
      3. Backlog vs Roadmap
         1. Backlog defines the product features for the near time.
         2. Roadmap structure : - Use metric-driven roadmap. - Success or weakness of a new product would be based on a metric.
         3. The scientific mindset : Think like a scientist, describe hypothesis -> define test -> Measure. The famous socrates method : https://tomprof.stanford.edu/posting/810
3. PRD : Product requirement document.
   1. Template :
      1. [Project Name] [one-line description] Team: [Awesome] Contributors: [PM], [Designer], [Engineer], [Analyst] Resources: [Designs], [Analytics], [Notes]
   2. Problem Alignment
      1. High level Approach Narrative Goals Non Goals
   3. Solution Alignment
      1. Key features Key flows Key logic
   4. Launch Plan
      1. Key Milestones Operation checklist
   5. Appendix
      1. Change-logs Open questions FAQ's
4. Release Management
   1. Plan release
      1. Timelines Delivery dates Requirements.
   2. Build Release
      1. Development Identify impediments and solve them
   3. UAT - User acceptance test
      1. Typical end-user test Ideally performed by PM with test leads.
   4. Prepare release
      1. Complete the VnV cycle.
   5. Deploy release
      1. Deploy to production. Perform conformance test.
5. Prioritisation - A ruthless way Making sense of firehose of Ideas.
   1. 1 : Customer feedback
   2. 2 : Competitive landscape.
   3. 3 : Sales and customer service
   4. 5 : Analytics and metrics
   5. 4 : Analyst Research
   6. To consider during prioritisation.
      1. How
         1. - Make it team activity, get different perspectives. - Limit the items we prioritise. - Categorise into strategic themes. - Understand customer value. - T -shirt sizing.
      2. Models
         1. RICE Reach Impact Consumer Effort.
         2. Impact vs ROI Prepare a weightage matrix.
         3. MSCow: Must, Should, Could, wont need
         4. - Performance benefit matrix. - Story mapping
6. By : Anjan kumar BR. www.linkedin.com/in/anjanbelgod