agile business analysis with mary gorman and ellen gottesdiener

TBAC 023 | Author Cast : Agile Business Analysis – Does it Exist?

by Yaaqub Mohamed a.k.a Yamo5

The Business Analyst Coach Podcast Artwork

Agile is making the rounds in almost every organization. There was a recent agile extension to the BABOK®, agile blogs are surfacing every other day and agile events are gaining increasing traction.  They say the future is in agile!

Really?

In this special and first three-way AuthorCast, I bring you one of the foremost experts in the world of agile to help demystify some of the misconceptions surrounding agile. We talk about how agile can add value to projects, what is the role of a BA in agile? what aspects of change can be approached using agile? How is agile gaining traction in the organizations and the perennial: Do we really need a BA in agile project?

To help answer all these, and many more thoughts around agile business analysis, here are Ellen and Mary:

The BA Coach podcast - listen on smartphone

Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

Sneak peek of the episode:

  • The idea of immediacy and identifying something valuable and within a very short timeframe.
  • Discussion around the narrow slice of business value and delivering it.
  • Traditional analysis vs agile analysis.
  • The importance of getting a shared understanding of the product needs.
  • Deliver something as quickly as possible to learn – do a research spike.
  • Taking agile approach to business case building activities.
  • Discussion around agile extension to the BABOK.
  • Why do we don’t need a BA on an agile project!
  • Discussion around scrum method / framework – product owner role, scrum master (team facilitator), & team.
  • How business analysis contributes to scrum teams.
  • BAs may blend into the delivery team.
  • When can BA be a product owner – situations that entail this.
  • Agile Jumpstart.
  • Coaching the analyst to become a scrum master.
  • Cultural changes in an organization when they tread on the agile path.
  • Four functional requirements … user role / the actions that product needs to provide / data / biz rules to enforce.
  • Importance of light-weight modeling.
  • Multi-modeling – analyze requirements at functional level.
  • Burning down and burning up work in value.
  • The BIG VISIBLE concept.
  • The mood board concept – visualizations of the product.
  • The agile traction in the industry.
  • Agile has moved into mainstream.
  • Every organization is at least piloting agile somewhere.
  • Why the term agile will go away.

Insightful quotes from this episode:

“The goal of the team is to deliver a valuable product – remove ur baseball cap that says BA on it… ”

“Every organization is at least piloting agile somewhere. ”

“We really don’t know what to build, until we start to build it…”

“There is huge value in getting feedback in what you build and how you built it as quickly as possible.”

“You are not leaving and coming back later, but you see the product evolve.”

“Deliver something as quickly as possible to learn – do a research spike… ”

“We are willing to do what matters to deliver value to the business. Period. “

Items mentioned in the show:

Ellen Gottesdiener in brief:

Ellen Gottesdiener is Principal Consultant and founder of EBG Consulting, Inc. Ellen has authored two books, numerous articles and contributed to several compilation books. She is a frequent speaker at national conferences and an industry advisor. Ellen develops all the training material used by EBG Consulting. Since 1991 Ellen has provided a broad range of services to EBG clients including consulting, mentoring, facilitation and training. Prior to founding EBG, Ellen spent 13 years as a manager, team leader, developer, and trainer with a major insurance and financial services organization.

Mary Gorman in brief:

Mary Gorman, Vice President, Quality & Delivery at EBG Consulting, assists project teams to explore, analyze, and build robust business and system requirements. Mary has over 25 years experience working with many organizations, including numerous Fortune 100 companies, as a consultant, mentor, trainer, facilitator, process engineer, developer, and analyst. Mary is a CBAP™ (Certified Business Analysis Professional™).

If you have any comments or questions for this episode, please post them below.

Enjoy the show and don’t forget to spread the word about this awesome episode using the social sharing links.

 


Featured Product -> The Ultimate BABOK® Kit

Unprecedented CBAP-CCBA Study Guide, BABOK eMindmap, eTables, BOK Cartoons, Audio and Video. The Ultimate All-in-One Study Aid is here.

Go to top

Article by

I am a passionate and practicing business analyst, author, and blogger from Toronto, Canada. I host this blog, and podcast to help business analysts throughout the world, do analysis better, by providing educational, relevant, and inspiring content. Musically driven by Eagles, Lucky Ali, and Linkin Park. Huge fan of Colts, Leafs, and Indian cricket team. To be in the loop for latest member-only resources, and news from The BA Coach be sure to sign-up for our free eNewsletter. View more BA passion painted with digital ink by Yamo!    

5 Pillars of a great BA

With this E-book, you will learn about the five pillars of being a great Business Analyst!. Sign-up below for our eNewsletter and receive your FREE copy once the book is launched! Sign up, or learn more!


{ 3 comments… read them below or add one }

Katie Metcalfe March 22, 2012 at 12:31 am

Thanks Yamo, Mary and Ellen for an interesting podcast about Agile Business Analysis.

I have a question for Mary and Ellen; what Agile techniques would you suggest introducing to a software development team that is currently not using the Agile approach but would like to get a “flavour” for the methodology.

Thanks again for the podcast and of course Ellen for the excellent books. :).

Katie

Reply

Ellen Gottesdiener April 5, 2012 at 5:23 am

Hi Katie:
Thanks for your note and query.

We like to think of Agile not as a “methodology” per se, rather as a disciplined discovery and delivery framework. The term “Agile” encompasses a number of methods such as lean, Scrum, XP, DSDM, Kanban, FDD, and more.

Here are some suggestions for “getting a flavor” for agile:

* Partition product delivery into planning horizons. Even if you don’t release to the customer for your shorter horizons, you complete a fully releasable product at the end of each delivery cycle. This takes enormous focus, discipline, and collaboration. Read this article for more info: http://ebgconsulting.com/Pubs/Articles/AgilePlanningAndAnalysis-SynergizingToDeliverValue.pdf

* Explicitly identify business value for all product partners (customer, business, technology). Value is in the eyes of the beholder (see: http://bit.ly/HpLJ7e ). Be clear how decisions will be made. Collaborate, collaborate, collaborate. (Some tips for collaboration/discovery workshops on agile teams are here: http://ebgconsulting.com/blog/agile-requirements-by-collaboration/ )

* It’s the goal, not the role. Analysis is the entire team’s responsibility. (see: http://bit.lygoalnottherole )

* As partners, explore options for product needs using the 7 Product Dimensions (users, interfaces, actions, data, controls, quality attributes and environments). Collaborate to assemble the highest value options for your next delivery cycle. Slice product needs into requirements (chunks) and as a team, deliver them in the shortest possible timeframe.

* Explore product needs using a combination of analysis models and examples (e.g., scenarios, acceptance tests, specs in the form of “given/when/then” or data tables). Pull the “testing mindset” forward. Consider specifying requirements with those examples and models. Don’t write classic textual specifications. Read more here (http://ebgconsulting.com/blog/agile-analysis-agile-testing-synergies-for-successful-software-solutions/ )

* Learn. Expect to “fail” to learn – it’s only failure if the team doesn’t use mistakes as a forum for improvement. Conduct retrospectives to “inspect and adapt” at regular intervals. (see http://ebgconsulting.com/Services/Retrospective%20Description%20EBG%20Consulting.pdf Honestly and transparently reflect on both process and product.

* The book Mary and I are writing provides specific, practical guidance and examples on these practices. Stay tuned for the book launch this summer. Details for pre-ordering will be in our eNewsletter. (You can sign up at http://ebgconsulting.com/newsletter.php)

all the best,
~ ellen and mary

Reply

Katie Metcalfe May 16, 2012 at 1:43 am

Thanks Ellen and Mary. You have given me lots to review and think about. Looking forward to the new book.

Reply

Leave a Comment

{ 2 trackbacks }

Previous post:

Next post: