Agile methods applied with Miro
Learn to use Miro as a visual aid for planning, coordinating and reviewing team work through agile practices adapted to your working context.
Find your starting point
A good fit when you want to represent work visually and practise planning and retrospectives in Miro.
Another option to consider
Teamwork with agile methodsIf you prefer to focus on working agreements and choose the supporting tool later, choose agile teamwork.- Hours and sessions
- 6 hours live · 3 sessions of 2 h.
- Group size
- Up to 12 participants per trainer as a reference, adjusted to the practice and feedback.
What you will learn
- 01
Represent a workflow with its states and blockers in a readable format.
- 02
Prepare a planning activity with explicit priorities and capacity.
- 03
Facilitate a retrospective and keep a record of an action, its owner and the follow-up agreement.
A proposed programme
You will build a visual board for a team preparing a campaign: represent the work, plan around capacity and review a blocker. The focus is on using Miro to support discussion and leave readable agreements, with a retrospective that ends in a concrete improvement action.
We adapt the selection and depth of the modules to the group's starting point and goals.
01Visualise the flow
Work boards and criteria for representing tasks, states and work limits.
You will work on
- Create workflow states with a visible criterion for moving each piece of work.
- Represent specific deliverables with an owner and mark blockers without confusing them with completed work.
- Review the board's readability with another person and retain an agreed source for tracking progress.
- Practice
- Represent a campaign's preparation with its assets, review and pending approval; explain where each piece of work sits and why.
- How you will check it
- A readable flow with movement criteria and a visible blocker that another person can find.
02Plan as a team
Visual activities for discussing priorities, capacity and dependencies.
You will work on
- Discuss priorities and dependencies before choosing work for the next working period.
- Compare proposed work with available capacity and agree what to leave out.
- Record the exercise's work-in-progress limit and review what to do when an asset becomes blocked.
- Practice
- Plan a campaign week with two agreed work slots and a pending external approval; justify what to start and what should wait.
- How you will check it
- A plan that respects the fictional capacity, makes dependencies explicit and does not add work merely to hide a blocker.
03Learn from the work
Reviews and retrospectives with documented agreements and follow-up.
You will work on
- Gather facts from the simulation before interpreting what helped or hindered the work.
- Facilitate a short retrospective distinguishing observations, hypotheses and proposals.
- Choose an improvement with an owner and date, and agree how to observe it in the next cycle.
- Practice
- Review the approval bottleneck and propose a checklist to use beforehand, with an owner and a review at the next planning session.
- How you will check it
- An improvement action connected to the observed problem and a specific follow-up, without claiming unmeasured results.
Make the blocker visible before adding more work
Teaching example
Suggested practice: build a board for a chosen process and rehearse planning and a retrospective. We check whether other people understand the flow and can find decisions and actions; situations are selected with the team.
Fictional classroom case. A team is preparing a campaign with one page and two communication assets. In the simulation, it agrees a maximum of two pieces of work in progress; the page needs external approval before it can be published.
- Starting point
- Every asset appears as “In progress”. There is no criterion for moving to review, and the page appears to be progressing even though it has been waiting for approval for two days.
- First attempt
- The first plan adds the second communication asset to make use of the time. The team exceeds its limit without reviewing the cause of the blocker or who should resolve it.
- What we review
- The trainer asks the team to keep the blocker visible, assign its follow-up and review capacity before starting another asset. In the retrospective, the group proposes checking approval requirements before submitting the next page.
- Result
- The page remains in review with approval pending and Lucía following it up. The plan leaves the second asset unstarted; the retrospective assigns Diego to prepare a checklist for review the following Monday. These are rehearsal agreements, not demonstrated performance improvements.
Prepare a campaign · maximum two items in progress
Not started
Second asset
Wait until capacity is available.
In progress
First asset
Diego · prepare the draft.
In review
Campaign page
Blocked · Lucía follows up approval.
Before closing
Approval received and changes reviewed.
Teaching illustration of a fictional case. The limit and states are exercise agreements, not a mandatory Miro configuration.
Before calling it complete
- States have movement criteria and the pending approval remains visible.
- The plan respects the agreed limit or explicitly records its revision.
- The retrospective connects a fact with an action, owner and review date.
Sessions to put it into practice.
Reference edition · 6 h live
Reference edition: 6 live hours across 3 sessions of 2 hours. The board, planning and retrospective are practised during the sessions. The flow, examples and any additional work are agreed around the group's context.
- Session 12 h
Build the flow and its working agreements
Represent campaign assets, define movement criteria and mark a pending approval on the board.
By the endA visual flow with states, owners and an understandable blocker.
- Session 22 h
Plan around capacity and dependencies
Choose priorities, respect the agreed work slots and rehearse replanning when work is blocked.
By the endA classroom plan explaining what starts, what waits and why.
- Session 32 h
Facilitate the retrospective and follow-up
Review facts from the rehearsal, choose an improvement and check with the trainer whether the board allows it to be picked up in the next cycle.
By the endA documented retrospective and an improvement action with an owner and review.
If your team needs to go further
- Implementing Scrum or Kanban across the organisation, supporting real work cycles or certifying agile skills requires a separate programme.
- Integrating the board with Jira or other systems, synchronising tasks or automating metrics is outside this reference edition.
Learn with someone who designs work systems.
Guillermo Mascaraque Piña
Work systems consultant
Over two years of experience designing systems for companies across industries and sizes.
Guillermo is the planned trainer for this programme. Dates, language and his availability are confirmed when the edition is agreed.
With guidance, practice and support.
Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.
Materials you can keep
Downloadable, versioned guides, exercises and review criteria for internal use.
To prepare and complete the delivery
A short recommendation, an editable communications kit and a group learning report.
TOF’s own certificate
A certificate of achievement after the agreed assessment. It is not a vendor certification.
A month of email support
On the content covered, up to two accumulated hours for the whole group.
Your team carries out the practice. Implementation services are agreed separately. See the scope →
Miro Solution Partner
As a Miro Solution Partner, we bring experience in visual collaboration and designing boards for teamwork.
Our partner profile ↗The partnership belongs to The Optimal Flow. Learn’s certificate is issued by TOF; it is not a vendor certification.