Skills for Success: Professional Development Day @ IIBA Minn / St. Paul

I will be giving a new version of my talk about Behavior Based Requirements at this year’s Professional Development Day in Minneapolis / St. Paul. I am excited because I have reworked the entire presentation to both show my passion and give attendees a chance to practice using the Given-When-Then requirements format.

The conference title is Skills for Success: Evolving as a Business Analyst and my presentation is “How to Use Behavior Based Requirements to Build Understanding & Save Your Project.”

The event is on Monday, April 15 at the Earle Brown Heritage Center outside of Minneapolis (registration link). This is one of the premiere PDD events in North America and I am honored to be speaking. If you are in the area, please come, engage, and learn from the outstanding speaker line-up and local BA community.

 

Post conference update: Here is the published version of my slides:

Mastering & Improving …

I am honored to be a guest contributor to ThoughtWorks Studios’ blog this week. This post coalesces some of my thinking about the effort Business Analysts should be putting forth to grow as individuals and as a profession. Please go check out and comment on Mastering and Continuously Improving Stories with Shu Ha Ri.

Image of post on ThoughtWorks Studios website

It was different writing a guest post for ThoughtWorks. I often ask for feedback on my posts before publishing them, but this was much closer to having an editor. The suggestions were deeper and more serious than I usually get from friends and colleagues. I think the post turned out better for it. Also, they wrote the title and suggested the calligraphy image. I suppose I could have asked or been insistent about changing these (Kristi doesn’t understand why this picture was chosen), but I was much more honored to be asked for this than I am concerned about the title and image.

I want a conversation about what it takes to learn and master our craft, so please do comment on the post!

Measuring the Analysis Process

I’ve previously written about measuring requirements and business analysts. I am concluding the series with my current thoughts on measuring the analysis process.

What_gets_measured_gets_done

This quote is a truism is because it’s how we work. Measurements help us identify areas we should focus on or improve. Measurements let us know when we succeeded, or not. I love the idea of measuring BAs and yet, I have spent years balking at the idea of measuring requirements and BAs. It doesn’t work very well in practice.* I had cause to rethink the how to measure BAs when one team I worked on took down the following action item, “Decide (if,) how and what BA velocity to track.”

Measuring Business Analysts; Don’t KPI Me

Good managers often ask, “How do I know my team is performing well? How can I spot which folks need help? Who should I reward for a job well done?” In today’s busy world, where managers have significant responsibilities in addition to nurturing their team, measurements and metrics can be a a help.

Unfortunately, it is really easy to measure analysts poorly.

book jacket

Read “Discover to Deliver”

In Discover to Deliver: Agile Product Planning & Analysis, Ellen Gottesdiener (author of The Software Requirements Memory Jogger and Requirements by Collaboration) and Mary Gorman tackle one of the largest problems facing Agile and Scrum software projects, how to successfully integrate the ideas and tools made so popular over the last decade into working, valuable solutions.