Deriving Business (User) Stories from your Business Architecture

For any kind of enterprise-wide change initiative, if you derive your backlog of Business Stories only from interviews with users, you may to end up with a patchwork of individual needs that don’t necessarily hang together, some of which will conflict with each other and which won’t give you the enterprise picture.

I have a problem with user stories

I admit it. I have a problem with user stories. Not with the Actor/Narrative/Benefit syntax or the idea of adding acceptance criteria or the idea of valuing conversation over documentation. I love all that. I have a problem with the name “user” stories.

I’ve been applying Agile principles for about ten […]

Decision models, user stories and acceptance criteria

In 2012 one of my readers contacted me to ask whether business rules and user story acceptance criteria could be considered the same thing. I answered in a blog post that they should not.

However, in 2013 I learned decision modelling, specifically, The Decision Model (TDM) and I was taught by […]

The 12 Agile Principles Adapted to Business Architecture

You are probably familiar with the Agile Manifesto that was written in 2001 by several forward-thinking software developers.

However, it is a manifesto for software development and, as you may have seen in a previous post, business architecture is about more than software requirements. Does that mean we cannot apply the […]