How-to guides

Backlog refinement, also known as backlog grooming is an agile practice that involves continuously reviewing, clarifying, and prioritizing the product backlog for upcoming sprints.

Run more effective backlog refinement sessions with these best practice tips and tricks.

A user story, much like a persona, adds context to your work and in turn value. So how do we write user stories? Better yet, how do we write good ones?

Easy Agile Programs offers a flexible Program Board / ART Planning Board right inside Jira, to provide a place not only to support the PI Planning ceremony, but also as a source of truth beyond planning as things adjust and teams continue to collaborate.

How our product, Easy Agile TeamRhythm, interfaces within your Jira instance from a data, usability and navigation perspective by answering some of our FAQs regarding our Jira integration.

The ability to split the story map by sprints or versions allows stakeholders to track progress at a glance and ensure over-commitment is prevented.

The purpose of PI planning is to bring together multiple Agile teams working within a program or large project to align their efforts, synchronize their plans, and establish a shared understanding of the upcoming Program Increment.

A story map is a visual representation of the journey a customer takes with a product, including activities and tasks they complete.

Using a birdseye view of your Backlog to visualise and organise your backlog in Jira.

By surfacing and visualising dependencies, you are able to quickly understand and communicate what teams are working towards together and where their work is dependent on each other.

The planning poker feature allows any logged in user viewing the ticket to cast their vote with regards to the effort required to get the ticket done.

The purpose of Pre-PI planning is to establish a shared understanding of the business goals, objectives, product vision, milestones and priorities, and to create a cohesive plan for successful execution.

Master the art of running effective retrospectives with these best practice tips and tricks

We know how important facilitation is to an effective retrospective. See how we've developed purpose-built features to help you run more effective retrospectives.

Retrospectives can improve the way we work together, as an agile team we want to share and discuss our thoughts, feedback and learnings from the previous sprint/version, and draw conclusions that we can implement.

‍

The main purpose of sprint planning is to determine which user stories or backlog items will be worked on, discuss the scope and define the sprint goals to establish a shared understanding.

On this page, we'll share 3 of our best practice tips for running effective User Story Mapping sessions.

User story mapping takes all your user stories (across all your persona types) and assigns them to epics in the order that delivers the most value to the customer.