product management process


Linkedcare

Objectives


  • Improve completeness of product requirements that enter the development pipeline;
  • Increase product backlog visibility throughout the company;
  • Allow anyone to contribute to the product roadmap;
  • Reduce the clutter in the current development;
  • Make it easier to see who is doing what;
  • Incorporate the future roadmap into the same process;
  • Prepare the process to handle a bigger engineering team;
  • Time box meetings; 

The Boards



Current Development Board

  • Next up:
    Prioritised, where we fetch the things to do
  • In progress:
    Under active dev or design.
    Assigned.  (put a face on it, never more than 2 per dev)
    With a predicted end date by the dev working on it
  • QA:
    Where the quality team will test it (in staging)
  • Launchpad:
    Reviewed and ready for production
  • Live:
    Approved and in production

    • Product Roadmap Board



    • All the major features for each quarter (looking at most 3 quarters ahead)
    • Moved into planning once the quarter begins

    Inbox Board

    • Ideas
    • Any company member can add his own ideas to this board

    Bugs board

    • Inbox:
      Where anyone can report bugs (replication path mandatory)
    • Needs input: 
      Dev team not able to reproduce the bug
    • Accepted:
      Reproduced needs to be fixed
    • Next week:
      Product manager moves the accepted into this column so that it gets into next week sprint

    ENGINEERING BOARD



    • Tasks that don't fit into the development category
    • Moved by the head of engineering as they are needed to complete other tasks

    PLANNING BOARD

    (where the magic happens)

  • Inbox:
    Where we move stories into
  • Needs input:
    Prioritised
  • Spec:
    Stories that need specs
  • Design:
    Stories that need a designer to look into them
  • Next Up:
    Ready to be moved into development




    • How all of this stuff moves

    (the dreaded meetings...)


    Product meeting



    • Monday morning
    • 30 minutes maximum
    • Everyone
    • Bugs fixed are presented (identified who corrected it)
    • Presented completed features (identified who worked)
    • PM presentes next up tasks 

    Inbox REVIEW



  • Friday morning
  • 30 minutes maximum
  • PM and Ideas owners
  • Idea owner present the ideas (max 3 ideas/person)
  • Solutions not discussed only problems

    • Product planning


  • Friday afternoon
  • 1 hour maximum
  • PM and Engineering team
  • Review all the cards from planning and engineering that are ready to come into the current development
  • Guarantee that the tasks are the right size and correctly explained
  • Attribute points (1 - easy; 2 - medium; 3 - hard)
  • Review all the bugs in the next up and pull them to the top of the queu

    • Standup


  • Every day (10 min max)
  • out of the boring "what have you done..." and focus on "what I need to accomplish my current task"




    • The Stories (the cards)


    product management process

    By alexmcpt

    Made with Slides.com

    product management process

    • 1,408

    More from alexmcpt