Methodologies
The seven built-in methodologies in Skopo and how to choose between them.
Skopo ships with seven built-in methodologies. When you create a project you pick one, and Skopo configures the right work-item types, board columns, rituals, artifacts, and metrics for that approach. You can layer optional practices on top of the base methodology, and you can migrate a project to a different methodology at any time through Project Settings.
Choosing a methodology
Ask two questions:
-
How does your team receive and commit to work? If you work in timeboxed goals (sprints or cycles), look at Scrum, Extreme Programming, or Shape Up. If work arrives continuously and you want to pull when ready, look at Kanban or Scrumban. If you need to validate ideas before committing delivery capacity, consider Dual-Track Agile. If you want minimal process, use Basic.
-
How mature is your delivery process? Scrum suits teams that need explicit cadences and ceremonies to stay aligned. Kanban suits teams that already have a reliable delivery system and want to optimise flow. Scrumban is a transition path between the two.
If you are unsure, Kanban is a good starting point for most continuous-delivery work, and Scrum is a good starting point for most product teams with a backlog.
Catalog
| Methodology | Best for |
|---|---|
| Scrum | Product teams that benefit from a regular planning and feedback cadence |
| Kanban | Continuous delivery, operations, and variable incoming work |
| Shape Up | Product teams that want fixed time, variable scope, and fewer backlogs |
| Extreme Programming | Software teams facing changing requirements and demanding quality needs |
| Scrumban | Scrum teams moving toward continuous flow or balancing planned and unplanned work |
| Dual-Track Agile | Product teams that need to validate opportunities before committing delivery capacity |
| Basic | Small projects and teams establishing their process |