Power Up Your Agile Planning & Analysis

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.

In the podcast, I discuss with Joe the metaphor that Mary Gorman and I have been using, “structured conversations.” Structured conversations are used to explore and evaluate product requirements and clearly identify what to build and when to build it. These conversations fuel daily work on agile/lean product teams, enable them to populate and groom their product backlog, and to quickly analyze requirements so requirements can be allocated them to delivery cycles. These practices are described in the book Mary and I are in the midst of writing.

I hope you find the podcast interesting!

Resources that extend the concepts and practices I presented at Agile NYC on 18 October 2011:    

• Podcast with Agile NYC founder Jochen (Joe) Krebs – recorded just before my presentation
• Agile Planning and Analysis – Synergizing to Deliver Value Better Software, May/June 2011 [note*]
• Slicing Requirements for Agile Success Better Software (feature), August 2010[note]
• It’s the Goal, Not the Role: The Value of Business Analysis in Scrum StickyMinds.com, June 2011
• Harvesting Stakeholder Perspectives to Organize Your Backlog StickyMinds.com, January 2011

[note*]

You’ll find the slicing narrative tracks to what I shared in my presentation. Since Mary Gorman and I wrote the article last year, we have adjusted our use of some terms.  You can equate:

Article term = Training term

Expand-Then-Contract = Explore and Evaluate

Element = Dimension

Object = Data Dimension

Business Rule = Control Dimension

*Joe Krebs books: