Product Development Process

I just went through the exercise of writing down what I think is a good product development process. It's a little more optimistic than realistic, but takes in to account the best things I've learned over the last few years. Obviously, I have the perspective of an even-tempered product manager (which is only a half-truthful self appraisal). For me, I'm best at and enjoy most steps 1-3.

What do you think? Am I missing anything major?



1.Concept/Brainstorming
Define goals, set parameters and brainstorm! *Partner* with the appropriate people during this phase, making sure that they have the opportunity to define the project with you. Include senior people whith a stake in the project. Define roles: who will lead the initiative, who has a voice, who will give the green light (these should vary from project to project).



2.Definition and Design
Come up with a solution for the goals, pulling from brainstorm as well as from any other sources. Put a stake in the ground and start defining what the product specifications are. These don't have to be air-tight, but simply be well-thought-out enough for you to be able to communicate to stakeholders. Often it's appropriate to deeply involve a developer or designer at this phase.

The design process often happens outside the formal product development process. Designers should be involved from the brainstorm phase and must largely deliver full design solutions and specs before development starts.

3. Consult
The goal of this phase is to get stakeholders on board with your idea. This can be informal or formal. This step isn't always necessary on small projects or when you have a very good idea of what these folks want.


4.Formalize/ Prioritize/ Schedule

Working with everyone that will actually be doing work (design, development, QA,etc) sit down and list out everything that needs to be done. You've already talked to these people in the consult phase, so now it's necessary to get every task (and problem) down on paper. Set out a realistic schedule and make sure everyone and everything lines up. Add or cut features and time to achieve the desired level of quality and timing. Get everyone to agree to these tasks and dates. Now you've got a project.


5.Approval
In step one, you defined who needed to approve the project. Don't make this a lot of people, rather make it 1-2 people that have the authority to greenlight. If you work at a place where you're not sure who these people are or where this list of people numbers more than 2, start looking for a new job.


6.Development
Build it. Have frequent check-ins to make sure everything is being built to spec and is progressing on time.

7.Acceptance

When it's done, have a meeting with the team to review the product. If it's done, great. If not, send the team back out to finish (or create a new plan).

8.Refine
Rinse, repeat.

No product is perfect on the first go. Do some testing, get customer feedback. See if you have time and resources to refine the product.

---