Great for PI planning and retros!
September 07, 2021

Great for PI planning and retros!

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Miro

Miro is used by several of the segments within the organization, with multiple enterprises I am aware of and multiple projects for teams/work functions within those. It is used for collaboration, knowledge sharing, and planning due to the idea it can be edited easily but acts as one version of the truth. The group uses it for PI planning as part of SAFe, and teams for diagrams and retros.
  • Architectural/product diagrams.
  • Team Retrospectives.
  • PI planning board.
  • Some developers feel draw.io is more user-friendly.
  • Permissions can sometimes be tricky.
  • Increased clarity and positive feedback for PI planning.
  • Improved productivity in team meetings for retrospectives and architectural discussion.
The use of Miro in the organization was implemented before I was a user, but I have had the experience of getting team members to sign up and gain access to the team project and relevant enterprise. This can sometimes be tricky, but I do appreciate some of this relates to organization policies rather than those set out by Miro.
Once again, I have had little view over the organization's integration of Miro. For the product areas I work with, integration wasn't particularly difficult but more long-winded. I do understand that the majority of this is due to organization-level policies rather than any limitations of Miro. The ability to add users from the organization who haven't requested access already would be beneficial.
Miro has certainly been useful for collaboration, most notably in the whole-company PI planning event (as per SAFe). We used to plan together in person and create a huge PI planning board with all features and dependencies mapped between teams, but due to the pandemic, our planning has gone remote. Miro is the best tool we have used so far to recreate this physical board and will be used for the foreseeable for this purpose.

Do you think Miro delivers good value for the price?

Not sure

Are you happy with Miro's feature set?

Yes

Did Miro live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Miro go as expected?

I wasn't involved with the implementation phase

Would you buy Miro again?

Yes

I personally prefer use of Miro to Trello, although Trello is easier to sort out access controls for, which may not necessarily be a Miro issue however. We use Azure DevOps extensively for development but have also used it for PI planning and team retros. Whilst the Deliver Plans view in Azure DevOps is useful, it is much more limited than using Miro for PI planning as dependencies are much harder to visually map. I also prefer using Miro for retrospectives, as Miro is more interactive and cards can be grouped and linked in more creative ways.
Miro is very useful for PI planning (as described in SAFe), as the entire program board is split by team, and iteration can be viewed and updated through planning by the development teams. Team retros are also easy to run on Miro, as you can use and create templates and easily group cards as desired. Using Miro for creating product diagrams is also fairly useful, but some developers prefer to use draw.io.