How to Choose the Right Delivery Approach for Complex Projects (Without Overcomplicating It)

When it comes to complex projects—especially those with strong and modernized information technology components like cybersecurity, artificial intelligence (AI), software development, or cloud modernization—the delivery approach you choose matters just as much as the technology itself. One of the most common questions is: “Should we use Agile or Waterfall?” For complex, technical work, the better answer is: you will likely need both.

Start With What You Already Know

Every complex project has elements that are predictable. Cybersecurity efforts must align to established frameworks. AI initiatives require data access and governance. Software and cloud programs depend on infrastructure, environments, and defined roles. Across all of these, there are approvals, funding considerations, and stakeholder expectations that don’t change. These are your foundational components. This is where a structured, predictive approach is valuable. As outlined in PMBOK®, predictive methods are well-suited for work that is clearly defined, compliance-driven, or dependent on sequencing and control. If the work is known, plan it with clarity. That structure creates stability for everything that follows.

Then Design for Discovery

As projects move beyond the foundation, new information begins to surface. User needs evolve. Data introduces variability. Integration reveals dependencies. Security considerations influence design decisions. This is where Agile becomes essential as this approach supports iterative, incremental delivery—allowing teams to build, test, and refine solutions based on real feedback. Rather than waiting for a final product, teams deliver usable components early and improve them over time. PMBOK recognizes adaptive approaches as particularly effective when requirements are evolving and uncertainty is part of the work. For complex IT initiatives, that flexibility helps reduce risk while maintaining 'moving forward' momentum.

Build Security In, Not Around

For most technology-driven projects, security is not a final step—it is part of the process.

DevSecOps extends Agile by integrating development, security, and operations into a continuous cycle. Solutions are built, tested, secured, and monitored in smaller increments, allowing issues to be addressed early rather than late. This approach aligns with modern cybersecurity expectations and key frameworks such as NIST, especially in orgnaizations where systems must be both fast and secure.

Keep Teams Moving Together

As projects expand across multiple teams and stakeholders, coordination becomes just as important as execution. This is where Scaled Agile principles—such as those found in SAFe®—add value. They emphasize systems thinking, incremental delivery, and alignment across teams, helping organizations maintain progress without unnecessary delays.

The goal is simple: keep work moving, keep teams aligned, and keep value flowing.

What This Looks Like in Practice

For complex projects with technical components, the most effective delivery model is often a tailored approach:

• Use predictive methods for foundational, structured work

• Use Agile for solution development and refinement

• Use DevSecOps to ensure secure, continuous delivery

• Use Scaled Agile principles when coordination extends across teams

This aligns directly with PMBOK’s emphasis on tailoring—selecting the right approach based on complexity, risk, and environment.

Bringing It All Together

Complex projects don’t require more methodology—they benefit from the right combination of approaches applied thoughtfully. When structure supports clarity and flexibility supports learning, projects move forward with greater confidence and less friction.

How Baron PM Transformation Can Help

At baronpmtransformation.com, this is where I focus—helping organizations select and apply the right delivery approach for complex, technology-driven initiatives that include:

• Assessing project complexity, risk, and technical uncertainty

• Identifying what can be planned vs. what should evolve

• Designing a tailored approach grounded in PMBOK, Agile, and Scaled Agile principles

• Applying an MVP-first mindset to validate solutions before scaling

• Aligning stakeholders, technology, and delivery processes from the start

Final Thought

Whether you’re launching a cybersecurity effort, exploring AI, or modernizing IT systems, the goal is to move forward with clarity, reduce risk early, and deliver solutions that work in real environments. You don’t need to overcomplicate project delivery. For complex projects with technical components, success comes from applying the right approach—at the right time—and bringing those approaches together in a way that keeps progress steady and outcomes meaningful.