So who does what? Roles and responsibilities. In Scrum, Scrum Master (facilitator and helper), Product Owner (voice of the customer), and team members.

Let’s explore how the customer journey map and story map play together to create a beautiful thing.

The perfect pair of superheroes - user stories (cards) and customer journey maps. Let’s explore how they work together.

There are five major events in Agile Scrum: release planning, sprint planning, daily standup, product demo, and retrospectives. The Uncommon League’s Practical Agile utilizes a 6th secret event for backlog refinement by assessing technical risk, prioritization, t-shirt size (s-m-l-xl) estimating, and story splitting for backlog items.

It is the journey we take or the steps we take along the journey that count?

Definition of Ready (DOR) is an essential concept in sprint planning. DOR is the criteria by which the team will accept a card into a sprint.

A Customer Journey Map is a diagram that shows the journey a customer or persona takes when going through your process with a particular focus on positive and negative points in their experience. A customer empathy map is an excellent technique to use in conjunction with this technique.

We find that the following 3 things are frequently ignored in Agile and in turn makes a team less productive and effective.

There are a lot of great retrospective techniques. Circles and Soups is our favorite.

Many approaches can be used for demos in Agile. Of course, there is the traditional meeting to walk through the changes, but after a few of these meetings, the team craves a new approach.

It's human nature to avoid difficult tasks. That leads to just doing all the easy stuff first and leaving all the problematic things for last. That sounds like a good plan, but leaving all the hard stuff to last means prioritizing capabilities and features based on your customer needs isn't going to be possible.

Here are high-level steps for how to determine Agile business value. Let’s figure out those metrics and measurements.

Epics by the themselves are not the answer. The answer lies in how you deconstruct.

Here are a few important things that a Business Analyst provides an Agile team.

What Are the Differences Between Pie and Tarts? It seems entirely off-topic for an Agile article but stay with us.

Part of practical requirements elicitation is less order taking and is more about asking probing questions to understand the business need more effectively. Understanding gives you the ability to analyze the requirements more deeply.

There are 9 pillars to Business Analysis. These pillars are used with the inquiry model to elaborate and elicit the business solution. There is a lot of cross-over between the pillars, but they support a solid business solution.

In this article, we'll dive into the exciting world of progressive elaboration, exploring its benefits, applications, and how it can revolutionize the way you manage projects, user stories (cards), and more.

It can be tricky navigating the first few months as a manager, helping your team adjust to your new role. Here is how to handle promotions from peer to boss.

Giving feedback is an art — and so is receiving it. Let’s look at this concept from both sides: giving and receiving constructive criticism.