Archive for the ‘Requirements Management’ Category

“Do The Right Thing” – PMI® Requirements Management Webinar Recap

Sunday, April 20th, 2014

ebgembedLast month I presented a webinar to the PMI® (Project Management Institute) Requirements Management Community of Practice: “Do the Right Thing: Adapting Requirements Practices for Agile and Traditional Projects.”

The Requirements Management CoP has grown exponentially and will continue to do so, especially since the PMI recently announced the new Professional in Business Analysis certification (PMI-PBA). This growth was reflected in the full webinar room during the live event. During the webinar, I shared requirements discovery and delivery principles and practices along a gradient from traditional to agile.

As you review the deck, there are some key points to know: Continue reading

Context Counts: Adapt Your Requirements Practices to Fit

Friday, February 21st, 2014

ShuHaRi Whether you are agile or more traditional, your challenge is the same: In order to remain relevant in today’s market, you have to discover and deliver the right thing at the right time. To do this successfully, you need to elicit customer needs and quickly choose from among many competing voices and options to determine what is truly essential and what can wait for a future release. That means selecting the requirements development and management activities that are most effective for your particular situation–whether those practices are in your current toolbox or not.

To understand this mindset shift, it might help to think of requirements activities in terms of the ShuHaRi progression, with a learning stage (shu), a breaking away stage (ha), and a transcendent stage (ri). 

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

Wednesday, June 19th, 2013

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 | 1 Comment

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

Thursday, May 9th, 2013

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

Tuesday, March 5th, 2013

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 | 2 Comments

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

Sunday, December 9th, 2012

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 | 11 Comments