Is the execution of an “embedded product development project” different from execution of conventional industrial projects [say mechanical , civil, etc.] ?
Understand this might be a common question which comes to most of our mind [IT professional].
In my experience, often have heard PM's saying embedded product development project [involving software and hardware development] is really tough, complex, etc. Hence, project failure rates are more.
Which I don't believe, all projects would have same characteristics.
If all projects are executed under the framework of project management [all knowledge area], then definitely failure rates could be reduced.
Any thoughts ? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Not at all. I was the leader of some high risk projects in the field, from creating embedded software in a medical device that test sugar in blood and inject insulin taking into account the measures to create a geostationary-satellite. There is no difference to any other type of project except, in my case, quality activities. But you have to remember that product requirements must be used to define project requirements (project scope) so no problem with that. Saving Changes...
While all knowledge areas will usually come into play in most projects, the extent to which specific practices and the level of rigor involved needs to vary based on the complexity and context of a project.
In certain types or domains of projects, specific contributors to complexity are greater (e.g. technology uncertainty vs. complicated stakeholder relationships) and hence the approach a PM and the team takes needs to be situational based on these.
"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened."
