One thing I find interesting about project management is how much the success of a project can depend on decisions made before the actual work begins. During the initiating phase, the team needs to understand the real business need, define clear objectives, identify stakeholders, and determine how complex the project may become.
I think this is especially important in medical device development because many different groups may be involved, including engineering, clinical, regulatory, research, and management. If these groups have different expectations from the beginning, even a technically strong project can run into delays, budget problems, or major changes later.
For me, defining the scope early is one of the most important steps. Clear deliverables, milestones, technical requirements, and limitations can help prevent misunderstandings and scope creep as the project moves forward. Spending more time at the beginning may feel slower, but it could actually save significant time and resources later.
Do you think companies sometimes rush through the initiating phase because they want to start development quickly? Which part of the initiating process do you think would create the biggest problem if it were skipped, and why?
I agree many companies and project teams can rush through the initiating phase, which certainly can lead to problems later in the project execution phase. As presented in lecture, consequences can include scope creep, underbudgeting, and unachievable deadlines. A thorough initiating phase can align expectations from the outset, as well as make execution easier by comparing to and learning from similar completed projects.
That being said, there are limitations to what can be accomplished in the initiating phase. Ideally, a perfectly executed initiating phase can prevent or minimize all obstacles that may arise during project execution. However, it is almost impossible to foresee all complications that can affect a project from the outset, especially if it is one that is unique.
Additionally, over-investing time and resources into the initiating phase may also detriment the project. Costs for the project often start from the outset, and stakeholders who cover these costs reasonably want to see progress for their investment. If a project spends too much time in this phase, these stakeholder may remove support for the project. Planning the perfect project doesn't mean much if you never get to execute the plan.
I believe the role of the initiating phase is to make sure the project team is set up for success by making sure the stakeholders and project team are aligned in expectations, and to anticipate major obstacles in execution.
Many points made above also apply to the planning phase. How do you think project teams should balance investing in the initiating and planning phases with making progress in the execution of the project?
@andrewg I would agree that working on the initiating phase for an extended period of time stagnates the project and can lead to deadline issues later on. However, I wouldn't say that less emphasis should be placed on the initiating phase to avoid these issues. Instead, I think that the initiating phase should begin as soon as the project is seen as promising to pursue by a company. Ideally this would occur months or even years before the desired deadline.
Even as a low-priority task, having a team or even a single worker working out the logistics and scope of a project for a little bit of time each day can result in many critical details of the project being already thought-out and considered by the time initiating the project becomes a higher priority. Adequate time should be spent in this phase due to the importance of a solid scope before the planning phase begins.
I agree that a strong initiating phase can prevent a lot of problems later, but I don't think it can prevent everything. One point from the lecture that stood out to me was the importance of talking to the people who will actually be doing the work. Working in manufacturing, I can see why this matters because sometimes something may look straightforward when it is being planned, but once you are actually performing the process, there can be small details or limitations that weren't obvious in the beginning.
For that reason, I think one of the biggest mistakes during initiation would be defining the scope and timeline without enough input from the people who will eventually execute the work. You can have clear objectives, milestones, and a budget, but if they aren't realistic from an execution standpoint, problems will probably show up later anyway. I also agree with Andrew that there has to be a balance because trying to predict every possible issue could keep a project in the initiating phase forever. Do you think the people doing the actual work should have a bigger role in defining project scope, or should that mainly remain the responsibility of the project manager and stakeholders?
All previous posts bring up a difficult issue: spending a lot of time in the initiating phase can cause the project to stagnate, and rushing through it may develop major roadblocks down the line. I definitely agree that companies sometimes rush through the initiating phase but there are important reasons as to why they want to start development so quickly. Companies often rush through the initiating phase because medical technology and patient needs can evolve quickly. They worry that spending too much time on scoping may cause the device to be outdated before its even built.
Not speaking to your stakeholders during the initiating phase would create the biggest problems if this part were to be skipped. This can lead to stakeholders adding minor requirements later on in the process because they weren't properly aligned on the boundaries from the start. This can also throw off the project timeline massively.
Another concern to have is that if the initiating phase drags on too long without defining specific milestones then it can cause teams or departments to get frustrated before the development starts. Timing is extremely important in any medical device project but it is also crucial to build flexibility in the initial scope to handle fast moving clinical environments.
@andrewg I agree heavily. While the initiating phase is extremely important, and can build a strong base for a project, investing too much time can derail the realization of the project. Thinking too much about how to do something can lead to that thing never happening. To your question, you can tell when too much deliberation is being put into the initiation phase when items are planned to absolute certainty, as this can put a restriction on the project and how it might need to change. While clarity should be built into the project, so should flexibility. By putting a hard deadline on the initiating phase rather than keeping it open-ended, you can force decisions and lead to a plan that isn't perfect, but thought out well enough.