Agile Business Analysis

Agile 2012 submissions

Last week I submitted a couple of sessions to the Agile 2012 conference. The sessions focus on two particular areas that are very close to my heart and where I see a great deal of opportunity for us to improve as a community.
more »

Agile Business Analysis – slides

This is the presentation that was delivered to both Agile 2010 and the Agile Business Conference in London.



MMFs – enabling incremental delivery

I just checked back to see how much I’d written about MMFs (minimum marketable features). This is a technique I use and talk about a lot so I thought I’d written more that I have.

I’ll provide here a few of the ways I use MMFs and why I feel that they are so helpful when devising incremental delivery strategies. more »

User stories discussed

Last week I had the pleasure of running a user story workshop for a group of very experienced folk with a broad range of backgrounds and skill sets. We convened the workshop to discuss the challenges that present themselves when we apply user stories for the first time on a real project.

The conversation was broad ranging but, since a number of people have told me that attending the workshop was valuable, I’ll try to capture some of the key issues.

more »

Agile Business Analysis at Agile2010

On Thursday Gary Jones and I will be talking about Agile Business Analysis techniques in E-3 at 13:30.

This post brings together some of the resources he will be referring to and other related references. If you have a favourite resource for other BA techniques please feel free to comment below.

more »

Splitting user stories

I should start this post with an admission – I do not claim credit for any original thought here. What follows is taken from my own notes and has been accumulated over a number of years. I most recently tweaked my own notes and the way I explain this stuff after hearing Jeff Patton’s talk from the UK Lean Kanban conference on infoQ.

The way I think of splitting user stories is through identifying axis. Some examples of axis are:

  • Steps in a workflow
  • Usability
  • Quantity of data
  • Asymmetric value
  • Stakeholder needs more »

Agile requirements – back to basics

Much has been written about User Stories however, it is still a subject that I find people struggling with.

In this post I intend to review what are the choices that we make that enable us to claim a requirements approach as agile and how can user stories (when applied well) help us achieve this agility.

An agile approach to requirements should

  • Defer investments
  • Support just in time elaboration
  • Encourage collaboration
  • Support planning

The most common approach to agile requirements is User Stories. A user story represents a need on behalf of a specific stake-holder. more »

Where am I?

 

September 2012
M T W T F S S
« Jan    
 12
3456789
10111213141516
17181920212223
24252627282930