Team Structure for MVP
In structuring a team for MVP, we should consider the following: there is a massive number of uncertainties. We have to work with assumptions and bets.
The goal for the business is to find a good enough solution for a reasonable budget: ROI. It’s vital to have the fastest feedback loop to prevent dramatic waste.
Here is how I see the team structure: #
Product Manager / Owner " title="Link to this section">#
They define the product’s vision, so the rest of the team will follow.
One of their functions is to communicate with all the product stakeholders (sponsors, developers, designers, customers).
They relay the vision and goals of the product to the team, so everyone follows the direction.
Helps with verifications and controlling the quality.
UI/UX Designer " title="Link to this section">#
The designers are responsible for designing the interactions between users and the product.
They conduct experiments and do research. They interview users, potential users, and stakeholders.
They create user interfaces that work great and are also pleasing to look at.
Developers " title="Link to this section">#
The developers write the code that delivers new behaviors.
They decompose big requests into small atomic chunks.
Make architectural decisions.
They aim to make the product error-free. Onboard Continuous Delivery by using automations, tests and code review.
They monitor performance because speed is a feature of every application.
Paul Keen is an Open Source Contributor and a Chief Technology Officer at JetThoughts . Follow him on LinkedIn or GitHub .
If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories .
Infographic from https://www.strategyzer.com/blog/posts/2015/4/23/5-lean-startup-essentials-to-reduce-risk-and-uncertainty Cover Photo by Austin Distel on Unsplash