Formal Processes

Formal product development processes have a preferential orientation toward control. Typically, a formal process is used when either the technology and/or the market is relatively mature. Routinely, management reviews predefined checklists and presides at decision point meetings (which are also known as gates).

Flexible and Agile Processes

When there is more uncertainty at the beginning of a project, a flexible and agile process should be considered. These projects are characterized by any combination of the following items:

• More interaction with customers throughout the project
• Continuous integration of market input data from the ideation and development phases
• Frequent project updates that may include daily, short team meetings
• More frequent milestones
• The acceptance of solutions that are adequate (instead of solutions that maximum performance and a longer development time)
• More prototypes that demonstrate working features
• More support from management to remove project roadblocks
• Greater budget flexibility
• Project members that exhibit a preference for team behavior (instead of committee behavior)
• Increased team flexibility and responsiveness to new information
• Team members that include top performers (high productivity, holistic viewpoints, self-directed,...)
• A leader capable of identifying critical path issues and mobilizing the team resources to rapidly resolve issues. The leader integrates information and can make the appropriate decisions.

If you already use a formal process and have defined checklists, OpLaunch can provide resources to design and develop the required deliverables - on time - with the quality that you require.

If you do not have a robust development and launch process, it is probably not reasonable to try to develop one and deliver a product within a few months. Often, a successful product launch is unlikely because of unrealistic expectations that may include any combination of the following:

• An overly aggressive schedule
• An unstable product feature set or feature creep
• Too many distractions
• An under-resourced team
• Missing expertise

OpLaunch's experience with both formal development methodologies and flexible/agile processes enable us to implement the proper solution for your current development and launch projects and to prepare you for more efficient solutions for your next project.

OpLaunch can provide immediate help when your project is in trouble. Our Launch Architecture services are intended for extended engagements with your development team. Our NPD-tuned services are intended to help your team meet your product launch deadline and achieve better results.