Agile guide · Agile practices
Agile Project Management Tools and Techniques
Agile is not about software, but the right techniques and tools make it much easier to practise. This guide covers the core techniques every Agile team uses and what to look for in a tool.
Key takeaways
- User stories, backlogs, boards, charts and retrospectives are the core techniques.
- Use the INVEST checklist for user stories.
- Choose tools that support your process, not the other way round.
Core Agile techniques
- User stories: short descriptions of value from the user's point of view: "As a [role], I want [goal] so that [benefit]."
- Product backlog: a single ordered list of everything that might be done.
- Story mapping: arranging stories along the user's journey to plan releases.
- Estimation: relative sizing with story points.
- Task boards: visualising the workflow.
- Burndown and burnup charts: tracking progress.
- Timeboxing: fixed durations for sprints and meetings.
- Retrospectives: structured reflection and improvement.
- MoSCoW prioritisation: Must, Should, Could, Won't have this time.
Writing good user stories
Use the INVEST checklist: stories should be Independent, Negotiable, Valuable, Estimable, Small and Testable. Add acceptance criteria to each story, often in the form "Given… when… then…".
What to look for in an Agile tool
- A product backlog you can order by drag and drop.
- Scrum and Kanban boards with customisable columns and WIP limits.
- Sprint planning with capacity view.
- Burndown, burnup, velocity and cumulative flow reports.
- Roadmap and release views.
- Integrations with chat, documents and, for software teams, code repositories.
- Read-only access for stakeholders.
Commonly used tools
Teams use tools such as Jira, Azure DevOps, Trello, Asana, ClickUp, Wrike, monday.com, Linear and Notion for Agile work. Many teams also start with a physical board on a wall. Features and prices change often, so trial any tool on a real sprint before deciding.
Avoiding tool traps
- Don't configure every field on day one.
- Keep one source of truth for the backlog.
- Don't let the tool dictate your process.
- Measure outcomes, not ticket counts.
Frequently asked questions
Do I need software Agile tools to be Agile?
No. A whiteboard and sticky notes work well for co-located teams. Software helps with remote teams, reporting and scale.
What is the best Agile tool?
The one your team will use every day and that supports your method. Test two or three options on a real sprint.
What are the most common Agile techniques?
User stories, a product backlog, story mapping, relative estimation, task boards, burndown and burnup charts, time-boxing, retrospectives and MoSCoW prioritisation.
What is a user story as an Agile technique?
A short description of value from the user's point of view, often written as "As a role], I want [goal] so that [benefit]." See [user stories.
What is the INVEST checklist Agile technique?
A test for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable.
What is story mapping as an Agile technique?
Arranging user stories along the steps of the user's journey, then slicing horizontally to plan releases that deliver a complete, usable path.
What is MoSCoW prioritisation as an Agile technique?
Sorting requirements into Must have, Should have, Could have and Won't have this time. It came from DSDM and is widely used in Agile.
What features should an Agile tool have?
An orderable backlog, configurable boards with WIP limits, sprint planning, burndown, velocity and flow reports, roadmap views and integrations.
Is Jira the only Agile tool?
No. Azure DevOps, Trello, Asana, ClickUp, Wrike, monday.com, Linear and Notion are also used. See our tool comparisons.
Can spreadsheets work as an Agile tool?
Yes, especially at first. A spreadsheet can hold a backlog and simple charts, though dedicated tools make boards and reporting easier.
What is the Given-When-Then Agile technique?
A format for acceptance criteria: given a starting context, when an action happens, then a specific result should follow.