Archive for the ‘Workshops’ Category

Power Up Your Agile Planning & Analysis

Friday, November 18th, 2011

I’m pleased to share my podcast with Jochen (Joe) Krebs*, Founder of Agile NYC. The podcast was recorded on October 11, 2011, just before my presentation to the Agile NYC group.

The presentation, entitled, Power Up Your Agile Planning and Analysis:

Deliver Value via Structured Conversations describes how product stakeholders partner to develop a shared understanding of the product needs. I discuss how the partners gain a focused yet holistic understanding of the highest-value requirements and plan the project so that the delivery team builds the right product, at the right time. Continue reading

Collaboration Works: Ingredients for Successful Workshops

Wednesday, October 26th, 2011

I’m honored to share my podcast with Yaaqub (Yamo) Mohamed of The BACoach. We discuss ingredients for effective requirements workshops described in my first book, Requirements by Collaboration: Workshops for Defining Needs.

Reflecting on My Personal Learning Journey

Tuesday, August 23rd, 2011

I’m pleased to share with you an “author cast,” a podcast interview of me by Yaaqub (Yamo) Mohamed of The BACoach.

Yamo’s interview got me thinking and reflecting on my own professional learning journey and dig into the two books I’ve written (so far 😉 ). Continue reading | 1 Comment

This Week’s Business Analysis and Requirements Workshop: 2 Days of Learning in Las Vegas

Tuesday, June 7th, 2011

I was recently interviewed by SearchSoftwareQuality editor Yvette Francino about this week’s Business Analysis and Requirements Workshop at the Better Conference/Development Conference this week in Las Vegas, Nevada (6-7 June, 2011).

Yvette asked me to explain the logistics, if we would be emulating gathering requirements for a particular project and if the workshop be relevant regardless of domain area. Here are my answers: As conference chair, Continue reading | 1 Comment

The Product Partnership: Using Structured Conversations to Deliver Value

Saturday, May 14th, 2011

In a prior blog post, you learned about the in-progress book Mary Gorman and I are writing. We are thrilled to have our workshop proposal for the Agile 2011 Conference accepted. The workshop will incorporates elements of our book. Here’s our YouTube video on The Product Partnership submission. Continue reading | 3 Comments

Ways to Understanding Product Functionality in the Absence of Documentation

Tuesday, March 15th, 2011

Have you been in a situation where there’s no documentation, yet you’re expected to understand functionality?

Trial transactions and observing behavior is one answer. But understanding context is also important.

Sue Burk suggests creative solutions in her expert response.

Agile Product Needs book: Sneak Peek

Wednesday, February 16th, 2011

Mary Gorman and I are in the midst of writing a book.  The title is still a WIP (work in process). A couple of contenders are “Agile Product Needs: <subtitle1:> ” and “The Agile Product Partnership: <subtitle2>”.  We’ll be looking for your help on settling on a compelling title – stay tuned, we can use your creative inspiration!

Our goal is to provide practical guidance on challenges agile teams face. Wrestling the “right” user stories out of the product backlog. Slicing user stories into “right-sized” chunks so they are ready for estimating and planning. Deciding on the next high-value product needs for delivery. Planning more than two weeks ahead (realizing you need a longer time horizon). Using acceptance criteria and examples to deepen shared understanding. Exploring product needs in a holistic way. … Continue reading | 5 Comments

What Inquiring Minds Want to Know: 120 Brains, 30 Minutes, 13 Themes

Thursday, January 13th, 2011

What Tough Agile Analysis Questions Do Business Analysts Need Answered?

This is the question I posed to the participants in a facilitated workshop at the Building Business Capability Conference (BBC) 2010 this past fall. The BBC conference, held in the Washington, D.C. area, was the first official IIBA ® conference. It offered tracks for business analysis, business rules, and business process management.

Context for the “Tough Agile Analysis Questions” Workshop

As the facilitator, I had 30 minutes to “crowdsource” from an energetic, curious, and motivated group of 120 business analysts. Many analysts in attendance were new to agile practices. All of them cared deeply about the value of business analysis. They were eager to… Continue reading

The 4L’s: A Retrospective Technique

Thursday, June 24th, 2010

by Mary Gorman and Ellen Gottesdiener

We liked it when a good thing took on a life of its own.
We learned that it really resonated with many folks.
We lacked sharing the full understanding of the technique.
We longed for more sharing.

Liked Learned Lacked Longed For

At the recent Deep Agile event, Mary briefly mentioned a 3Ls’ technique she used in a recent  retrospective (Liked, Lacked, Longed For).  A few folks tweeted about it, and it took off in the web’o’sphere

To fulfill our longing to share and provide some background, keep reading to learn how we use this technique.

Many moons ago we… Continue reading | 16 Comments

Agile Requirements: Not an Oxymoron

Friday, June 18th, 2010

Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons—self-contradictory phrases, often with an ironic meaning.

Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?

Once More into the Breach

Traditionally, defining requirements involves careful analysis and documentation and checking and rechecking for understanding. It’s a disciplined approach backed by documentation, including models and specifications. For many organizations, this means weeks or months of analysis, minimal cross-team collaboration, and reams of documentation.

In contrast, agile practices—leanLean, Sscrum, XP, FDD, crystalCrystal, and so on—involve understanding small slices of requirements and developing them with an eye toward using tests as truth. You confirm customers’ needs by showing them delivered snippets of software. Continue reading | 1 Comment