Before you choose a project management framework, you need to understand the nature and characteristics of your project. Is it well-defined or ambiguous? Is it predictable or uncertain? Is it simple or complex? Depending on your project type, you may need more or less flexibility and control in your framework. For example, if your project is well-defined and predictable, you may benefit from a traditional framework, such as the waterfall model, that follows a linear and sequential process with clear deliverables and milestones. However, if your project is ambiguous and uncertain, you may prefer an agile framework, such as Scrum or Kanban, that allows for iterative and incremental development with frequent feedback and adjustments.
-
Topic is vague; Project Type But discussion starts around definition of project or scope of work. AI team need to rationalize and not to mix up words/thoughts in this exchange of ideas. Thank you
-
Figure out what your project constraints are. Are you being held to a defined scope and schedule? Traditional waterfall methods with traditional project controls would be sufficient. If you have flexible scope or no deadline, agile project management may be fitting. The two frameworks have different measures of success and "control."
-
In my experience, implementing the appropriate framework is dependent on review of the scope, deliverables and appropriate milestones, which broadly ascertains the lay of the land. This will help to define time lines and any risks/ issues as proceeded by wider touch points and plans. Ultimately this will help to craft the framework and drive the delivery plans with target milestones to fruition.
-
True. Another consideration is what the business requires in terms of predictability of delivery commitment. It may be necessary to put some lightweight structure or time box around the ambiguity such as with a stage/gate model. This also opens the door to a hybrid Agile/Waterfall approach during the development phase.
Once you have identified your project type, you need to align your framework with your project objectives. What are you trying to achieve with your project? What are the expectations and needs of your stakeholders? What are the constraints and risks that you face? Your framework should support your project objectives and help you deliver value to your stakeholders. For example, if your project objective is to deliver a innovative product to a dynamic market, you may need a flexible framework that enables you to experiment, learn, and pivot quickly. However, if your project objective is to comply with a strict regulation or standard, you may need a controlled framework that ensures quality, accuracy, and documentation.
-
This is great advice. I would extend it a bit further and seek that all members of the team understand not only the project objectives but as well the reasons and perspectives that drives those objectives. More understanding and context all members of a team have, the more nimble and efficient the group will be at identifying opportunities and issues that may need to be resolved to reach those objectives. The other item to be aware of is objectives should be straightforward and simple metrics to understand. The framework should ideally be as simple as possible while being able to clearly define the objectives.
Even if you have selected a suitable framework for your project type and objectives, you may still need to customize it to your project context. Your project context refers to the specific factors and conditions that affect your project, such as your team size, skills, and culture, your organizational structure and policies, your industry and domain, and your external environment and stakeholders. Your framework should fit your project context and help you overcome the challenges and opportunities that you encounter. For example, if your team is distributed across different locations and time zones, you may need to adjust your communication and collaboration tools and methods. Or, if your industry is facing a disruption or a crisis, you may need to revise your assumptions and plans.
-
I'd also add the idea of building buffers into project structures. For example, an extra day or two around a particularly hefty part of the project plan can provide space for additional iterations that enhance the effectiveness of the project but don't add time. Doing this especially at the beginning of a project can ensure work is getting done effectively without pushing out due dates, which will enforce the need to stay on track while also succeeding. Striking that balance especially early on will build trust and show team members they can achieve both without added stress.
Finally, you need to evaluate and improve your framework performance throughout your project lifecycle. You need to monitor and measure how well your framework is helping you achieve your project goals and deliver value to your stakeholders. You also need to identify and address any gaps, issues, or inefficiencies that arise from using your framework. You can use various tools and techniques to evaluate and improve your framework performance, such as feedback surveys, lessons learned sessions, audits, reviews, and retrospectives. The key is to be open-minded, willing to learn, and ready to adapt to changing circumstances.
-
I think it is important to acknowledge that no two projects are the same and expecting all projects to conform to a said framework might be somewhat limiting. The framework should be designed in a way to allow for a certain amount of fluidity in project let alone programme delivery. Control can also take many forms - budgetary controls, risk mitigation and controlling the project scope so having a good indication from the project sponsor as to what are the areas that can and cannot be compromised often presents a good way to start.
-
In addition to balancing flexibility and control, project success hinges on stakeholder engagement, risk management, effective communication, resource optimization, change management, continuous improvement, and stakeholder satisfaction. Engaging stakeholders, managing risks, fostering collaboration, optimizing resources, adapting to change, learning from experiences, and delivering value are key elements to consider for successful project outcomes.
-
Start with max flexibility possible. Continuously de-risk your project. Work with a Murphy’s law in mind all the time, be most diligent about eliminating any potential problems. As project progresses ensure that all stakeholders know that flexibility will reduce and control will only increase. Finally push, push, push the project beyond the finish line in time and within budget! Easier said than done but experience will give you the intuition of the right mix of flexibility and control at any given stage of project and the eye for the potential risks most in need of mitigation during the current project stage! Good Luck!
-
Realize that everything is flexible until it is done...and even then can be modified...everything! The purpose of project management is to utilize that flexibility to arrive at the destination. The goal itself is flexible and may change at any time during the process. The project manager then must be fluid and knowledgeable of all factors and status of the project in order to strategically adjust to keep the trajectory moving towards the end. Control becomes directing the flow via channelling all of flexibility to the desired end. A moving ship is easier to guide than one anchored in port so keep your navigator close and hand on the wheel and wind in your sails as the only constant is change.
-
Here is specific example where a particular outdoor decorative light post style was specified in a contract. This was to match the existing deco lights in the park. The contractor had trouble getting the specified style and the work was in danger of being delayed. The contractor suggested a different, yet similar style. This was rejected at first by various stakeholders. Upon further investigation it was found that the pre-existing light posts were of various styles, no doubt installed at various times over the years. When this was pointed out, the contractor was allowed to install the style they suggested. The stakeholders were satisfied and the project could move along. Sometimes a little investigation of your surroundings pays off.
Rate this article
More relevant reading
-
Project ManagementHow do you follow project management standards and frameworks?
-
Project ManagementHow do you align your project management with your company culture?
-
Thought LeadershipYou think you know project management. But do you know the most common misconceptions?
-
Research ManagementHow can you build adaptability into your project management processes?