Lemon #65. Stages of a tech product

Lemon #65. Stages of a product

While reading ‘Inspired’ from Marty Cagan, we learned about the stages of a tech product: 

He says that everything starts with ideas. In most companies they’re coming from inside (executives or key stakeholders or business owners) or outside (current or prospective customers).

Now, most companies want to prioritize those ideas into a roadmap, and they do this for two reasons. First, they want us to work on the important things first, and second, they want to be able to predict when things will be ready.

To accomplish this, there’s usually some form of quarterly annual planning session in which the leaders consider the ideas and negotiate a product roadmap. In order to do that, they need a business case. 

Once the idea makes it to the top of the list, the first thing that’s done is for a product manager to talk to the stakeholders to flesh out the idea and to come up with a set of ‘requirements‘. 

These requirements might be user stories of a functional specification. Their purpose is to communicate with the designers and designers what needs to be built. 

Once the requirements are gathered up, the user experience design team is asked to provide the interaction design and the visual design. 

Finally, the requirements and design pecs make it to the engineers and this is usually where Agile finally enters the picture. 

The engineers will typically break up the work into a set of iterations – called ‘sprints’ in the Scrum process. 

Once we get the green light from QA testing, the new idea is finally deployed to actual customers.

Remember: 

  1. Ideas
  2. Business case
  3. Roadmap
  4. Requirements
  5. Design
  6. Build
  7. Test
  8. Deploy

Marty Cagan @ Inspired.

Jorge Moreno

shared by

Thanks for Reading

Enjoyed this post? Share it with your networks.

Leave a Feedback!