SPM - Project Management

[Tommaso2]

Hi all,

About Project Management:

Waterfall is the standard project type, but with Agile Development plugin it is possible to install Agile.

What about Hybrid?

Which is the concrete difference in the platform among the three types?

In this regard I found that different “Link and Lists” are available, can you please provide additional details?

Many thanks,

Tommaso

[Namita Mishra · Accepted solution]

Hi @Tommaso2 ,

This feature of progressive UI (on selection of execution type) was first introduced in SPM (that time it was ITBM) in New York release.

Prior to New York, there was no impact \ difference on project UI on selection of execution types...

Now I don't think anyone will question on why it was introduced so I will leave that point... rather I will focus on the difference and when you should use what....

Project supports three execution methodologies—Waterfall, Agile, and Hybrid. These methodologies define how work in projects are planned, managed, and delivered. 

 

1. Waterfall Execution Methodology

As we know, waterfall is a traditional, linear project management approach where each phase (e.g., initiation, planning, execution, closure) is taken up sequentially.

In SPM this methodology:

• is used primarily for projects managed in Project Portfolio Management (PPM).

• Project tasks and milestones are planned in advance.

• No iterations or continuous delivery; progress is tracked through Gantt charts.

• Time, cost, and scope are fixed before execution begins.

This methodology is typically selected for:

• Projects with well-defined requirements and minimal expected changes.

• Regulatory or compliance-based work.

 

2. Agile Execution Methodology

Agile is an iterative and incremental approach focusing on collaboration, customer feedback, and small, rapid releases.

In SPM:

• Work is executed through Agile Development 2.0 module.

• Work is typically tracked using epics, stories, and scrum tasks. You can choose not to use scrum tasks.

• Teams work in sprints using scrum boards or Kanban boards.

• On the Agile Development 2.0, you can also perform Big Room Planning using the Agile Board -> Program -> where you can see the different teams' work across the sprints and their dependencies.

This methodology is typically selected for:

• Software development and projects where requirements evolve over period of time.

• Organizations adopting Agile or SAFe practices.

3. Hybrid Execution Methodology

Hybrid combines both Waterfall and Agile practices—in other words, work is planned in traditional way of project planning whereas execution happens in agile way.

Using this methodology, you can :

• Link a  project (waterfall) to Agile stories/epics/features via integration with Agile Development 2.0.

• PMO (in PPM module) manages the overall timeline and budget, while Agile teams (in Agile Development 2.0 module) manage day-to-day work.

• Enables visibility and reporting across both execution types.

• Supports mixed delivery models, some folks call it as Water-Scrum-Fall.

This methodology is typically selected for:

• Organizations transitioning from Waterfall to Agile.

• Large programs where governance is needed but work is executed using Agile.

Below are the areas where you will see the difference on selecting the execution type

• Related Links
• Related Lists
• Anaytics - you will see different dashboards as per the selected methodology.

NOTE: You can change the execution type from Agile \ Waterfall to Hybrid however, if you try to change the execution type from Hybrid to Agile or Waterfall, system will show a warning message. You can choose to ignore the warning message and continue... This is because Hybrid has both tasks and user stories \ epics and changing to more restrictive type (Agile \ Waterfall) will result in loosing some of the planning items of that project.

In Summary: 

Feature	Waterfall	Agile	Hybrid
Planning	Upfront, sequential	Iterative, incremental	Combination of both
Flexibility	Low	High	Medium
Tools in SPM	PPM module	Agile Development 2.0	Both PPM and Agile / SAFe
Governance	High	Lower (managed by scrum teams)	Balanced
Use Case	Infrastructure, compliance	Software dev, fast changes	Enterprise-wide or complex work

Value Add: 

Having Waterfall, Agile, and Hybrid in SPM is not just about project management — it’s about enabling strategic execution at scale. It empowers every level of the organization — from developers to executives — to work in harmony toward shared goals.

For example:

1) It bring the enterprise-wide Flexibility: 

• Different teams, departments, or business units can work in the way that suits them best — Waterfall for infrastructure, Agile for product teams, and Hybrid for complex programs.

• SPM doesn’t force a one-size-fits-all methodology.

2) Informed & Adaptive Decision-Making:

With all methodologies in one place, PMO & other executives can:

• Rebalance portfolios based on performance.

• Shift investments from waterfall to agile as needed.

• De-prioritize or pivot initiatives based on real-time data.

• Whether a team is delivering via a Gantt-based project or agile sprints, all work rolls up into a single strategic portfolio view.

• get real-time status updates, KPIs, and progress tracking across all types of work.

Hope this helps and if it does please mark this as correct answer to help me and the community.

Happy Monday !!

Thank You!
Namita Mishra

[Tommaso2]

@Namita Mishra Thanks a lot! Enlightening!

[Namita Mishra]

Pleased to know that you found it enlightening.... 

Thank you @Tommaso2  !!