Progressive elaboration always comes into play. The more you interact with something, the more thoroughly you understand how it works, and the better you can predict its behavior.

There are 8 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.

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.

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

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

Does every user story really need an epic?

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

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.

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

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

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’re making a little jump across the pond. Jen Battan from the Uncommon League will be speaking at the Business Analysis Conference Europe on September 20-23, 2021.

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.

It’s the over journey versus the parts of a journey that are the difference.

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.

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

Getting a certification or certificate is a big step in your career, but with so many certifications available, answering these questions can reveal the right path towards your career goals.

Yes, the Product Owner and team should be tracking Tech Debt. Keep a list of all those ugly trolls lurking in your product is an excellent approach to better managing the product stability. At some point, you are going to have to deal with them.

In Agile, the product roadmap layouts out when the capabilities and features will be deployed for a product. Product roadmaps prioritize significant features or capabilities into a series of releases, with each release building on each other to deliver the overall product vision.