This article explains the two project management approaches available in TeamDynamix (TDX): Waterfall and Agile. It is intended to help departments understand the differences between the two options and select the approach that best fits their type of work.
The goal is not to require departments to become project management experts, but to provide enough context to make an informed and practical choice when setting up a project in TDX.
Table of Contents
Overview
Overview
When a project is created in TDX, departments are asked to select a project management approach. This choice affects how work is planned, tracked, and displayed throughout the life of the project. TDX supports both Waterfall and Agile approaches. Each approach is valid, and neither is considered better by default. The most appropriate option depends on the nature of the work being performed.
(You will be prompted to select either Card Wall or Waterfall when developing your initial plan for the project. In this specific case, the Card Wall is an agile feature. This is where the user’s decision will be solidified)
Waterfall Project Management
Waterfall is a traditional project management approach where work is planned in advance and completed in defined phases. Each phase is typically completed before the next phase begins.
Common phases may include:
- Planning
- Design
- Execution
- Review
- Completion
In a Waterfall project, the overall scope and timeline are generally established early and change infrequently.
How Waterfall Works in TDX
In TDX, a Waterfall project:
- Uses tasks and milestones to track progress
- Follows a more linear sequence of work
- Is well suited for projects with clearly defined requirements
Progress is measured by completing tasks and moving through planned phases.
When Waterfall is a Good Fit
Waterfall is often appropriate when:
- The project requirements are well understood from the start
- The work follows a predictable sequence
- Changes are expected to be minimal
- Formal approvals or compliance steps are required
Examples include policy development, system upgrades with fixed scope, or facilities-related projects.
Agile Project Management
Agile is an iterative approach to project management that focuses on completing work in smaller segments over short periods of time. Rather than planning all work upfront, Agile allows teams to adjust priorities as the project progresses.
In TDX, Agile work is commonly managed using Sprints and the Cardwall.
How Agile Works in TDX
In TDX, an Agile project:
- Organizes work into short time periods called Sprints
- Uses cards to represent individual work items
- Tracks progress visually on the Cardwall
- Supports ongoing adjustments as work evolves
Agile emphasizes visibility, collaboration, and incremental progress rather than strict phase-based planning.
When Agile is a Good Fit
Agile is often appropriate when:
- The work is exploratory or evolving
- Requirements may change over time
- Progress is best tracked in smaller pieces
- Ongoing collaboration is needed
Examples include process improvement initiatives, application development, and cross-functional projects with changing needs.
Key Differences Between Waterfall and Agile
|
Project Area
|
Waterfall
|
Agile
|
|
Planning style
|
Detailed planning upfront
|
Planning occurs continuously
|
|
Structure
|
Linear and phase-based
|
Iterative and flexible
|
|
Change management
|
Changes are limited
|
Changes are expected
|
|
Progress tracking
|
Tasks and milestones
|
Cards, Cardwall, and Sprints
|
Recommendation for Departments
The PMO Office recommends all Projects initially create a "Waterfall" plan to establish high level project deliverables, checkpoints, and validations. Then, if a Project is more suitable for Agile, a separate Cardwall plan can be created which provides the specific team tasks required to support key deliverables outlined in the Waterfall Plan.
If the Project requires a full Waterfall Plan due to its attributes described above, then this Project Plan will be filled in with more detail to support the process.
Agile in TDX:
- Works well with the Cardwall
- Makes progress visible without complex planning
- Allows departments to start small and adjust over time
- Reduces the need for detailed upfront documentation
That said, Waterfall remains a strong choice for projects that are highly structured, time-bound, or governed by fixed requirements.
Departments should choose the approach that best aligns with how their work is actually performed, rather than trying to adapt their work to fit a specific methodology.
Additional Support
- OU Technology Center
- 44 Oakland Center
- Rochester, MI 48309-4479
- (248) 370-4357
- Office Hours: M-F 8:00am - 5:00pm