On this page
Short answer: a methodology is a way of working, such as waterfall, agile or SAFe. Software is where you record the work. Pick the method for each project from the work itself, then pick a tool that does not force one method on every project.
The common mistake
Teams buy a tool and inherit its method. A board-only tool pushes everyone to Kanban, even for a fixed-date construction fit-out. A Gantt-only tool pushes sprints into phases. The tool should follow the project.
Which method for which work
| Work | Fits | Why |
|---|---|---|
| Fixed scope, fixed date, many dependencies | Predictive | Plan once, track against a baseline |
| Changing requirements, a product that evolves | Agile | Short cycles, frequent re-prioritisation |
| Fixed milestones for sponsors, flexible delivery for teams | Hybrid | Gates above, sprints below |
| Many teams on one product | SAFe | Shared cadence and planning |
What a tool must do to support this
- Per-project approach. One project plans with a Gantt chart, another runs sprints.
- Shared governance. Risks, minutes, reports and documents should work the same way in all of them.
- Common roll-up. A portfolio view that compares them, whatever their method.
- Conversion. Switching a project's approach should not mean starting over.
How NUSK handles it
Each project picks its approach:
- Predictive: Gantt, WBS, milestones, dependencies and baselines.
- Agile: backlog, sprints, Kanban, standups and burndown.
- Hybrid: milestone gates for sponsors, sprints for the teams.
- SAFe: Agile Release Train, PI planning and program board.
Everyday delivery tools, such as meeting minutes with actions, timesheets, approvals, finance and documents, work the same in all of them.
How to decide
Ask four questions:
- Is the scope fixed or does it change?
- Is the date fixed by a contract or event?
- Who needs to see progress, and in what form?
- How many teams share the work?
Answers lean predictive when scope and date are fixed, agile when they are not, and hybrid when the answers differ for sponsors and the team.
When NUSK is not the right choice
If your whole organisation has standardised on one method and will not change, a tool built for that method may be simpler.
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.