Why Are Embedded Projects Always Delayed?

Follow+Star Public Account, don’t miss exciting content

Author | strongerHuang

WeChat Public Account | strongerHuang

The boss requires the project to be completed in three months, but after six months, it is still not done.

Is this situation something you often encounter?

Recently, I saw friends in the group discussing similar issues, so let’s talk about: Why Are Embedded Projects Always Delayed?

Unclear Requirements

When doing a project, the first step is the requirements.

If there are no clear requirements, 99% of projects will be delayed.

The first reason is vague requirements from the client, the client asks to create a product similar to a certain product’s functions.

If you don’t communicate the details deeply and immediately start the project, there’s an 80-90% chance that the product you produce won’t satisfy the client.

The second reason is that client requirements change at any time, for example: the client wants to create a temperature sensor that collects data and displays it on an LED screen.

After a while, the client says to add a humidity and wind speed sensor.

After another while, the client requires that these sensor data can be viewed on both mobile and computer.

。。。。。。

With this kind of project management, it will definitely never be completed and will never be done well.

Underestimating Project Difficulty

When we receive a project, we first conduct a comprehensive assessment based on the requirements, including technical details, development cycle, etc.

However, some people just like to boast, don’t follow the usual route, and start working directly, thinking the project is similar and can be completed in no time.

For example: some people have done small cars in school and think making a robot is very simple.

The project keeps dragging on, and in the end, they barely deliver a not very complete product.

Cost and Procurement Control Issues

Embedded projects are tangible products, not virtual products; a chip, or even a resistor can affect the overall cost of the project.

Most of us have experienced the chip price surge in the past two years; not only did the prices go up, but crucially, they were also hard to obtain.

In this context of rising prices and unavailability of components (chips), do you think the project will be delayed?

Poor Project Management

Large companies usually have a complete set of management systems, but many small companies have almost no management at all. Thus, the project tends to be very chaotic.

For example, unreasonable planning, resource management issues, or poor communication can all lead to delays in electronic product development.

In embedded systems, the problem of “passing the buck” often occurs—Is the circuit problematic? Is the program problematic?

Of course, because management requires a lot of human and material resources, it is normal for small companies to lack management in these areas.

Other Reasons

Real product development is different from playing around in the lab; there are many factors to consider. Here are some factors that may influence delays.

Regulatory Compliance: Electronic products must comply with various regulations and standards. If these regulatory requirements are not met in a timely manner during development, it may take additional time for adjustments and reviews, leading to delays.

Supplier Issues: If the suppliers you rely on encounter problems, such as delivery delays, quality issues, or bankruptcy, it can negatively impact project progress.

Human Resource Issues:A lack of skilled and experienced personnel can affect development progress. Staff turnover, training needs, or insufficient personnel can all lead to delays.

Testing and Verification: Electronic products need to undergo rigorous testing and verification processes to ensure their performance and stability. If testing reveals design flaws or performance issues, additional time will be required to address these problems, thus extending development time.

。。。。。。

In the end, how many projects have you messed up?

———— END ————

● Column “Embedded Tools”

● Column “Embedded Development”

● Column “Keil Tutorial”

● Selected Tutorials from the Embedded Column

Follow the public accountReply “Join Group” to join the technical exchange group according to the rules, reply “1024” to see more content.

Click “Read Original” to see more shares.

Leave a Comment Cancel reply