Project Execution Process
 

We have learnt from our experience that managing an embedded system project to ensure successful completion requires the same skill as managing any other system project.  We have evolved a methodology whereby a microcontroller project is completed within 12 weeks - this includes design, artworking and building/debugging of a prototype.
 

The clarity with which one answers the following questions, reflects on the project performance.
 

• What do we want to develop ? How clear can we get on this ? 

• Can we split the expertise and knowledge available into :

• Things we are sure of ? 
• Things that we think we can be sure of ? 
• Things where we are uncertain about ?

• What is the project goal? Do we believe that if we reach 80% of the stated goal, the purpose is achieved ?

• What resources do we already have ? What are the new resources available ?

• How do we propose to develop it ?

• Who is the leader who will lead, guide, manage and control the project ? Who are the other team members ?

• When do we want this project to get over ? What are the time based deliverables associated with the project ? 

We have seen that in all the projects where we were late on deliverables, the most common factor was that the user requirements had not been thoroughly analyzed and documented. Also, when we analyze the successful projects, feedback was :

Clarity of requirements was high

• An analyis of the time spent on the projects showed :

Our development model has evolved from this analysis and the benefits accrued are :

• Projects on schedule
• Shorter development lead times
• High customer satisfaction.
• Lower costs

Click here to view a powerpoint slide on software/hardware development process