Tuesday, June 21, 2011

Requirements Tips for Data Centric Projects

Are you working on data-centric software products? For example, ones that involves building a data warehouse, using extract-transform-load (ETL) and getting the gold—delivering business intelligence and analytic reports and queries for business decision makers?

Sue Burk shares the value of scenarios to define acceptance tests, and other practical techniques to improve your success with these data-centric projects in her expert response. Continue reading

Share
Tuesday, June 7, 2011

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

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

Share
Saturday, May 14, 2011

The Product Partnership: Using Structured Conversations to Deliver Value

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

Share
Thursday, April 7, 2011

Are Your Software Development Practices Jumping the Shark?

By Ellen Gottesdiener and Mary Gorman

In September 1977, the TV sitcom Happy Days had über-hip Fonzie, clad in leather jacket and swimshorts, water ski over a shark to prove his mettle—and at that moment even diehard fans knew that the show was past its prime. They were right. After that episode, ratings plummeted, and the expression “Jumping the Shark” was born. When a TV show, or anything else, jumps the shark, you know it’s on its way out.

Our question this month: have any of your software development practices jumped the shark?

For example, are there boundaries around people’s roles? Some organizations tend to confine people to roles such as developer, architect… Continue reading

Share
Tuesday, March 15, 2011

Ways to Understanding Product Functionality in the Absence of Documentation

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.

Share
Wednesday, February 16, 2011

Agile Product Needs book: Sneak Peek

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

Share
Thursday, January 13, 2011

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

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

Share
Saturday, December 4, 2010

Analysis Debt, Redux

Mary Gorman and I wrote an article on analysis debt Better Software. In it, we said that, like technical debt, teams can incur analysis debt by either ignoring analysis (a potential pitfall of agile teams) or overinvesting in analysis (a potential pitfall of traditional teams).

In a private exchange, one article reader took me to task. Referencing our table of Analysis Debt Causes, he wrote, “I see poor requirements work that would result in an inadequate solution, no matter how well [the product] built.” Furthermore, he said, “all the Remedies [in your article] are really requirements best practices.”

I was glad to hear his perspective because it prompted me to… Continue reading

Share
Monday, November 1, 2010

Agile Requirements by Collaboration

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

Share
Wednesday, September 29, 2010

Presentation Skills for Technical Professionals

“Oh drat”, you think.

“I’ve got to do a presentation!”

Nevertheless, you smile and ask, “Oh, sure—what’s the date?”

Presentation Skills for Technical Professionals to the rescue!

Out comes Naomi’s Karten’s splendid book. You open it, eager for your sit-down with your personal presentation skills coach.  You are easily captivated by Naomi’s clever style and practical guidance on presentations, and grateful for the online references and resources that supplement the text. Reading this book not only prepares you for your upcoming presentation; it also helps you get in the groove and enables you to gain confidence as you prepare. You actually enjoy the process!

I was flattered when… Continue reading

Share