Archive for the ‘Business Analysis Training’ Category

Boosting Confidence: 9 Practices of Great Agile Teams

Tuesday, September 29th, 2015

Confidence

We’ve noticed something about the high-performing agile teams we work with: their confidence. They truly believe and trust in their individual and collective abilities. Their confidence extends to how they go about managing their product and delivering value, continuously.

Inspired by Lisa Crispin’s blog, we have compiled our own list of confidence-boosting practices that we suggest when coaching agile teams. We hope they’ll help you and your team as you strive to discover and deliver great products. Continue reading | 3 Comments

Business Analysis for Business Intelligence

Thursday, February 2nd, 2012

Over the past few years, I’ve spoken to user groups to share my experiences working with use cases, scenarios, and user acceptance tests in support of data warehousing and Business Intelligence (BI) BI analysis. Afterwards, many people ask me to summarize my recommendations. In response, I wrote a short article – Requirements Tips for Data Centric Projects. You can access it here (note: you may have to register).

In my article, I focus on analyzing the context of usage. In addition, remember this: to elicit, analyze, and specify requirements in this space, almost all of the time-tested data-centric techniques are still necessary.

People often asked me for additional tips and advice. What additional considerations for business analysis for BI? Continue reading

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

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

Agile Requirements by Collaboration

Monday, November 1st, 2010

By Guest Blogger Rob Elbourn, Scrum Team Lead working at a major financial concern in UK. Visit Rob’s Agile78 Blog

I recently attended the “Agile Requirements by Collaboration” presentation at Skills Matter lead by Ellen Gottesdiener from EBG Consulting. Here are some of the main points I got from it.

Ellen described how collaboration needs to happen on several different levels of granularity along the way requirements are viewed on agile projects– the product (which establishes the product or portfolio roadmap), the release and the iteration (or work-in-progress).

Exploring these views can occur in several different facilitated workshops, from the roadmap workshop, to the release workshop to iteration workshops. The corresponding requirements that are clarified or driven out from these workshops also appear on different levels – boulder, rock and pebble.

The idea is that the pebbles form your user stories and are driven out at the level of the iteration workshop. Projects can encounter rock sized requirements at the iteration level and suffer a time delay as new pebble requirements are chipped off from them. This brings to question the level of “doneness” for a user story. Continue reading

Being Agile when Designing and Playing Agile Games

Friday, July 30th, 2010

By Mary Gorman

In my Stickyminds.com column “Playing at Work: Agile Games Deliver Value” I share game ideas and experiences – the benefits games can provide, selecting an appropriate game, facilitating a game, and designing a winning game.

Designing and Facilitating Agile Games

When writing the column I got to thinking how agile principles could provide a basis for good game design and facilitation. I reflected on a recent experience I had at Deep Agile 2010: Empowering Teams with Agile Games. Working in a small group we created a new game, tested it, and retrospected both the game and our design process in less than half a day. We consciously (and some times unconsciously!) were being agile! (To see and learn more about our game, read Michael Sahota’s summary at The Backlog Is in the Eye of the Beholder.)

Games and The Agile Manifesto

To clearly communicate the agile-ness of our work and what we learned I did a quick mapping to the Manifesto for Agile Software Development. 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 | 17 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