Maintaining Feature Parity Across Platforms

In the PMHQ Slack community, we regularly get thought-provoking questions that we feel should be explored in-depth and documented for future reference. We’re starting a new set of Q&A posts to dive into these kinds of questions, and enable everyone in the community to revisit the answers and contribute further!

“For the first time, I’m working on a product that spans multiple platforms (iOS, Android, macOS, Windows, Chrome). What are best practices for organizing teams and maintaining feature parity when targeting multiple platforms?” 

Neil Littlejohns, Director of Product Management at TunnelBear

Here’s my framework for tackling the problem of feature parity across multiple platforms. Continue Reading

Are We Product Managers or Problem Managers?

This is a guest post that was originally published by Jen Ruffner on Medium.

Problems should be the foundation of product development

We’ve all been to those planning meetings where the conversation starts to go on a tangent and the team starts suggesting ideas that don’t actually solve the problem that you started talked about. I like to call them headless ideas. And as the person leading the meeting, you have to go into damage control. It starts with a delicate dance of slowing the current momentum & corralling the conversation back to the problem.

Why and how does this happen? So much of product management glorifies coming up with great ideas and giving feedback. Also the wider you go in the organization combined with the closer you get to the pixels; the more feedback you’re going to get. Continue Reading

What is the Waterfall Methodology?

Waterfall Methodology

When starting new projects, companies face a decision of choosing which development methodology to use and one methodology that has historically been very popular is the Waterfall methodology. Development methodologies are simply a way to organize the workflow of product (usually software) development and there are pros and cons to each methodology. In this post, we’ll discuss the strengths and weaknesses of one specific methodology: Waterfall.

The Waterfall approach is a sequenced method of events that usually follow:

  1. Idea
  2. Analysis
  3. Design
  4. Development
  5. Test
  6. Final Product

A team will first come up with an idea which they will analyze in order to determine and prioritize business needs and requirements. Next, they focus on the design phase where the business needs are translated into technical requirements (i.e. decisions about which tech stack to use). Once all of these business / technical needs are finalized, the team can begin the code development. After development, the team begins code, systems, and user acceptance testing in order to fix any issues before they deliver the final product. Continue Reading