I think project planning is really important because it helps the team know exactly what needs to be done and when. Without a plan, people might get lost, tasks might get repeated, or deadlines might be missed. A good plan also makes it easier to see problems before they happen. For example, if you notice two big tasks are scheduled at the same time, you can fix it before it causes a delay. At the same time, I know that no plan is perfect. Things change, and sometimes you need to adjust along the way. I feel like the best projects are the ones where the team plans carefully but also stays flexible. That way, you’re not wasting time re-doing everything, but you’re also not stuck following a plan that doesn’t make sense anymore. What do you think, is it better to spend a lot of time planning every detail, or to just start and figure things out as you go?
I don't think that having a detailed plan, and having a flexible plan are mutually exclusive.
I don't think that having a detailed plan, and having a flexible plan are mutually exclusive. You can plan for details ahead time in a way that does harm the flexibility of your project. Actually, I believe that incorporating details in your project plan and schedule should instead improve the flexibility of your project. For example, if you need a material for some part of your project you could plan order it so arrives a week before the task it is needed for. Planning for this detail now would be detail oriented. However, as you have recognized that you need this material far ahead of time you can order it so it arrives a month ahead of time which now gives your project far more flexibility in when that task can be completed. Additionally, you can recognize small seemingly insignificant tasks that need to be done in your plan without actually creating a set schedule for them at first. You can decide the exact execution of these small tasks later during the actual execution, maintaining the project's flexibility but still having the detail planned for. Now, if something happens that prevents one of these small tasks from occurring, you are able to recognize it right away from your project plan or schedule without getting blindsided the day the task needs to be done. Another theoretical detail would be planning for routine tasks executed by another team or group. If for example your project relies on a piece of equipment that is part of a routine calibration or maintenance program, you may plan your schedule so that there is a buffer between your team activities, and the routine task so that any deviation from their schedule does not impact your project. Additionally, if this equipment does not have any routine or preventative maintenance done on it you may arrange for it to be maintained ahead of time so that it does not unexpectedly break on you causing delays in your project. Incorporating extra details into a project plan should improve flexibility as you identify potential failure points that could not be seen by omitting those details. Things can be figured out later and yet still be planned for in a way that does not impact project flexibility.
Also, I don't think that you should ever be stuck following a plan that doesn't make sense (even if reality is otherwise). If you are ever stuck following a plan that doesn't make sense anymore, I don't think that is really a failure of the planning phase especially. I think that is more of a failure of the control and monitoring of the project and should be brought to the project lead's attention immediately.
Over-planning sounds like it would lead to a more straight-forward project, however it could complicate risk management processes. While meticulous planning could account for many risks, there is always a chance something is overlooked. What if the alternative for a process fails? What if an entire section of a project is overlooked? Meticulous planning also takes time. The time it would take to carefully plan out each and every small detail involved in a medical device project may not be ideal for certain companies. Deadlines and budgets are important, so planning out a project very meticulously might not be productive. I believe that "figuring out as you go" is the result of poor planning. The project plan should give a clear outline of where, how, and when a project should progress, as well as providing a set of alternatives to consider when the project might be delayed. The extent to which a project plan should be developed with is a point of discussion as well. How far should a project be planned out? Should the project plan leave some room for problem solving or should it be clear-cut? What are some of the most overlooked processes in a medical device project?
