Posts on Analysis

Rope Your Scope: Reining in Scope Creep (Part II)

Slide1Last time, I told the story of a team that experienced a breakthrough after clarifying the scope of a stalled project. Noting that scope creep—the unrestrained expansion of requirements as the project proceeds—is cited as one of the top project risks, I promised to describe some of the good practices that help product partners manage product scope in a disciplined way. With clients, I always stress the importance of developing a product vision, identifying goals and objectives for the product, and clarifying the product partners’ value considerations very early in the project before development proceeds. Let’s look at ways to do that.

Continue reading

Rope Your Scope: Reining in Scope Creep (Part I)

scope creep image 2- contextRecently I worked with a project team developing a software product under grant from four entities, with a government agency as their ultimate customer. They called me in because, three months into a four-month project, they were desperately behind. Why? They’d been spinning in circles, trying to satisfy diverse stakeholders who had overlapping as well as conflicting requirements. The funding was split among several competitors, each with its own competencies, and there was a sense that the government agency was playing favorites based on its own preferences in the domain.

Continue reading

Cure Your Agile Planning and Analysis Blues: The Top 9 Pain Points

frazzledproductchampionIf you’re on a team that’s transitioning to lean/agile, have you experienced troubling truths, baffling barriers, and veritable vexations around planning and analysis? We work with many lean/agile teams, and we’ve noted certain recurring planning and analysis pain points.

Mary Gorman and I shared our top observations in a recent webinar. Our hostess, Maureen McVey, IIBA’s Head of Learning and Development, prompted us to begin by sharing why we wrote the book Discover to Deliver: Agile Product Planning and Analysis and then explaining the essential practices you can learn by reading the book.

Continue reading

Using “Given-When-Then” to Discover and Validate Requirements

By Mary Gorman and Ellen Gottesdiener

In our book Discover to Deliver: Agile Product Planning and Analysis we discuss the usefulness of the “Given-When-Then” technique to explore (discover) and confirm (validate) product options. Here we summarize the technique*, brainchild of Dan North.

What it Is 

Given-When-Then (GWT) is a structured format for expressing scenarios with example data, including pre- and post-conditions.

Usefulness

GWT helps project stakeholders (business, customer and technology partners) communicate using business domain language. You can use GWT to explore product options and confirm selected options and confirm selected options, in a concrete, tangible way. Often called “specification by example,” GWT provides living documentation for your delivered product. It simultaneously specifies requirements while identifying acceptance tests, thereby streamlining discovery and delivery.

Continue reading

A Visual Language for Product Teams

In October, we wrote about big concepts for delivering an ever-evolving, high-value product. These Agile/Lean concepts are used in your daily work to rapidly discover product needs and deliver valued products:

* The Product, and the 7 Product Dimensions
* The Structured Conversation metaphor (explore-evaluate-confirm)
* Value
* Product Partners
* Planning Views

Continue reading

A Quick Dip into our new book – Discover to Deliver: Agile Product Planning & Analysis

How do you rapidly discover product needs and create a practical plan for delivering high-value products? How do the people on your product development team collaborate as partners to explore and evaluate which work to deliver next? How do you confirm that you’re building the right product in the first place? How do you incorporate Agile/Lean practices into your daily work?

Our newly released book, Discover to Deliver: Agile Product Planning and Analysis (two years in the writing) addresses these tough questions.

Here’s a quick tour of the big concepts.

Continue reading

Announcing the release of Discover to Deliver: Agile Product Planning & Analysis

by Mary Gorman and Ellen Gottesdiener

We are pleased to announce our book Discover to Deliver: Agile Product Planning and Analysis is now available.

Discover to Deliver provides the essential planning and analysis practices you need to collaboratively deliver high-valued products. It gives you a visual language to streamline and simplify your planning and analysis. You and your team get practical guidance in how to collaborate continually to discover and deliver an evolving product.

Continue reading

Structured Conversations at Agile 2012

What really is value? How do you get diverse stakeholders with sometimes conflicting views of value to obtain—and sustain—a shared understanding of product needs?

We discussed these questions and more with Tech Target’s Melissa Webb. Melissa interviewed us to learn more about our Agile 2012 tutorial The Product Partnership: Using Structured Conversations to Deliver Value.

Melissa’s interview synthesizes a number of the key concepts in our new book, Discover to Deliver: Agile Product Planning and Analysis, which will be released at Agile 2012!

You can read the complete interview here.

Going to Agile 2012?

We’re also pleased to be delivering workshops, each chock-full of learning activities:

That Settles It! Techniques for Transparent and Trusted Decision-Making on Your Agile Team Wednesday morning, August 15, 2012 with Ellen Gottesdiener.

The Contracting Two-Step: Patterns for Successful Collaborations, Wednesday afternoon, August 15, 2012 with Mary Gorman.

Hope to see you there!

Continue reading

Essential Agile Business Analysis

For years and years we’ve coached and trained teams how to elicit, analyze, and manage requirements for software development projects. We also work on projects—so our coaching and training is based on real project work. We’ve just written a book on agile product planning and analysis. Now that so many organizations adopting Agile as the method of choice, what about requirements? Is there a need for analyzing requirements in Agile?

That was the theme of our June Webinar titled (spoiler alert!) “Business Analysis Is Essential to Agile Success” (use training@ebgconsulting.com to login). For our blog eNewsletter readers, here’s the nugget: requirements drive agile teams!

Continue reading

Experiencing Agile: 6 Agile Planning and Analysis Practices to Try

What practices can you adopt to help your team experience Agile?

This question was raised by a listener to the podcast we recorded on agile analysis practices with BA coach Yamo. (Find the podcast here.) The specific question that Katie Metcalf asked us was this:

“What Agile techniques would you suggest introducing to a software development team that is currently not using the Agile approach but would like to get a flavor for the methodology?”

Continue reading

EBG Product Agility Newsletter

Get tips, stories and news on product discovery & delivery

Join our community and receive periodic tips, stories, and news on agile product management, product ownership, backlog and value management, collaboration, teamwork, and more.

Sign up Here