Project
1. Introduction of Sanplex features
1.1. Core Management Framework
1.1.1 Program
1.1.2 Project
1.1.3 Product
1.1.4 Execution
1.1.5 Management Models
1.2. Dashboard
1.2.1 Getting Started with Tutorials
1.2.2 Quick Add
1.2.3 Notification Center
1.2.4 Effort Tracking
1.2.5 Dashboard - Project and Execution
1.2.6 Dashboard - My Work, Contribution, and Recents
1.2.7 Dashboard - Approval
1.2.8 Contacts
1.3. Program
1.3.1 Program List
1.3.2 Program Kanban
1.3.3 Create Program
1.3.4 Create Sub-Programs
1.3.5 Project Charter Management
1.4. Product
1.4.1 Create Product
1.4.2 Manage Modules
1.4.3 Multi-Branch and Multi-Platform Management
1.4.4 Manage Plans
1.4.5 Manage Requirements
1.4.6 Requirement Reviews
1.4.7 Requirement Status and Phase
1.4.8 Create Releases
1.4.9 Track Progress
1.4.10 Business Requirements and Multi-Level Requirements
1.5. Project
1.5.1 Scrum Project
1.5.2. Waterfall Project
1.5.2.1 Manage Project Phases
1.5.2.2 Project Design
1.5.2.3 Project Matrix
1.5.2.4 Project Reports and Earned Value Management
1.5.2.5 Project Baselines
1.5.2.6 Project Change
1.5.3. Kanban Project
1.5.3.1 Set Up Kanban Projects
1.5.3.2 Configure Kanban Boards
1.5.3.3 Use Kanban Boards
1.5.4 Hybrid Agile Project
1.5.5 Hybrid Waterfall Project
1.5.6. Project Settings
1.5.6.1 Project Setup
1.5.6.2 Project Executions
1.5.6.3 Project Requirements
1.5.6.4 Project Builds
1.5.6.5 Project Tests
1.6. Admin Settings
1.6.1 Confluence Data Import
1.7. Workflow

Hybrid Waterfall Project

2026-03-28 16:07:15
Sanplex Content
414
Last edited by Jing WANG on 2026-08-25 15:30:55
Share links
Summary: Learn how to create a Hybrid Waterfall project with Waterfall +, configure phases, and use sprint-based Executions and Kanban boards within the Waterfall project structure.

Sanplex provides a Hybrid Waterfall project management model that combines Waterfall-based phase management with sprint-based Executions and Kanban boards within the same project. In the current Sanplex interface, this management type is displayed as Waterfall +.

Teams can use phases to organize the overall project structure and use Executions or Kanban boards within individual phases according to their delivery needs.

I. Create a Hybrid Waterfall Project

Go to Project > Create Project. On the Select management type page, select Waterfall +.

Select management type dialog with Waterfall + highlighted for combined Waterfall, Scrum, and Kanban project management.

On the Create Project page, complete the required project information. The project type is shown as Waterfall +, and you can select the appropriate Project Workflow from the available workflows.

Click Save to create the project.

Create Project page for Waterfall + showing project workflow, duration, linked products, plan, budget, and manager settings.

II. Manage Top-Level Phases

After the project is created, the system opens the Phase Setting page, where you can define the top-level project phases.

At the top level, the Method is Phase. Configure each phase by specifying information such as its Name, Manager, Type, planned dates, and milestone setting.

The phase types shown in the project can include Story, Design, Development, Test, Release, and Summary and Review.

Phases at the same level can be reordered, and additional phases can be added as needed.

Waterfall + Phase Setting page showing top-level phases with Type, Method, planned dates, milestone settings, and actions.

Top-level phase management follows the same general workflow used in a standard Waterfall project. For more information, see 7.5.2.1 Manage Project Phases.

III. Manage Subphases, Executions, and Kanban Boards

Within a top-level phase, you can create additional items to further organize and manage the work.

Use the actions for a phase to add a child item. The Method determines how that item is managed:

  • Phase — creates another subphase.
  • Execution — creates a sprint-based Execution within the phase.
  • Kanban — creates a Kanban board within the phase.

For example, a Development phase can contain both an Execution for iterative development work and a Kanban board for continuous delivery activities.

At the top level, only phases can be created. Within a phase, you can create subphases, Executions, or Kanban boards. Executions and Kanban boards cannot be further subdivided.

Waterfall + Phase Setting page showing Phase, Execution, and Kanban methods within project phases and the method hierarchy guidance.

IV. Use Executions and Kanban Boards

Executions in a Waterfall + project use the same sprint-based management workflow as Executions in a Scrum project.

For details about creating and managing sprint-based Executions, see:

Kanban boards in a Waterfall + project use the same Kanban management workflow described in the Kanban Project section.

For details, see:

V. Key Differences

A Waterfall + project retains the phase structure of a Waterfall project while allowing different management methods to be used within individual phases.

The hierarchy follows these rules:

  • Top-level items are created as Phases.
  • A phase can contain another Phase, an Execution, or a Kanban board.
  • Executions and Kanban boards cannot be further subdivided.
  • The Type identifies the functional purpose of an item, while the Method determines whether it is managed as a Phase, Execution, or Kanban board.
  • The functions available within the project vary according to the phase type and management method.

This structure allows teams to maintain an overall Waterfall project framework while applying iterative or flow-based management to specific parts of the project.

VI. Other Project Features

Other project management features in a Waterfall + project follow the same general workflows described for standard Waterfall projects.

For detailed instructions, see:

Write a Comment
Comment will be posted after it is reviewed.