When To Deviate from Project Methodology

Following a project methodology ensures that your project team, customers, and sponsor know what to expect and makes the project team’s efforts predictable. However, there are times when diverging from your methodology may be the best thing to do to ensure project success.

• Unexpected challenges occur. When market conditions or technological disruptions change suddenly, the methodology might decrease your team’s ability to respond. For example, a competitor releases an update to their product earlier than expected, and it’s better than your organization’s product. Expediting a project to stay competitive could be more important than methodology. For example, could the project team switch to agile practices even if the original plan was waterfall-based? Or you might consider shortening deliverable review periods and other time savers.
• Constraints impact the project. Tight budgets or limited personnel might require a shift away from methodologies that require specific resources or timelines. Simplifying processes or adopting lean principles could be more effective in these situations. By eliminating non-essential tasks to focus on what’s essential, the project might progress despite constraints. Note: Reevaluate the risks associated with eliminated activities to make sure the project’s risk level is still acceptable before you proceed.
• Team dynamics make the methodology cumbersome. The dynamics of the project team can influence a methodology’s effectiveness. If the team thrives on spontaneity and creativity, a rigid structure may stifle innovation. For example, asking a team in research and development (R&D) to follow the same methodology as other project teams could be counterproductive. That’s because R&D work needs more flexibility and creative problem-solving approaches to deliver better project results.
• Partnerships are involved. When a project involves novel solutions requiring extensive collaboration with an external organization, deviation from the standard methodology may be needed. First, the partner organization may use a different project methodology because of the products they create. Second, the teams may be concerned about confidentiality that the methodology would expose, such as sharing test data. (Test data often derives from customer production data, which might reveal information that shouldn’t be shared.) 

Consider carefully before you make a decision like this. Do you have a valid reason to make this change? Don’t make it unilaterally. Talk to your teammates and management first.

For more about project management methodologies, check out my Project Management Foundations course.

Coming Up

Office Hours Live – What’s wrong with project management these days? October 3, 2024  5PM MT Several aspects of project management don’t get much attention from management, project managers, and project teams. In turn, project management software sometimes ignores those areas as well. Bob McGannon and Bonnie Biafore will discuss these topics, so you don’t skip important duties. And they will talk about what to do if your software doesn’t cover them. Topics include: The 40-hour work breakdown rule (myth?) Estimating Cost management Project management versus work management Choosing the correct project management methodology Scheduling in waterfall and iterative projects Prioritizing project work versus operational work. To sign up, here

Office Hours Live – Learning Microsoft Project: Ask Me Anything October 8, 2024 1PM MT My updated version of Learning Microsoft Project is now available in the LinkedIn Learning library. To celebrate, I’m holding an Ask Me Anything (AMA) Office Hours on October 8, 2024, at 1pm MT. Whether you take this updated course now or you’re an experienced Project user, this hour is for getting answers to questions you have about MS Project. (If there is a wild outpouring of questions, I will host another event in November.) To sign up, click here.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 77,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________