Skip to main content

Users telling stories

It seems simple enough.  The project sponsor tells the business analyst what they want; the business analyst structures these requirements and documents them; the systems analyst translates this into a technical design; the developer implements the design; everyone checks it and then it goes into production.  Only everyone knows its not that simple.

The idea of a "User Story" seems simple too.  The project team, which includes someone from the business unit, identify a feature that someone will need in the system.  They write it in a simple format: "As a , I want , so that I get .  They agree how they will know when the feature is implemented satisfactorily.  They give an estimate as to how long it will take, decide its priority, and if the priority is high enough then they implement it.

This idea of user stories originated in Agile project methods and have several advantages over more traditional techniques for gathering requirements.  They are written in the language of the business rather than the technology.  They are short and apparently simple.  They can be clearly prioritised.  They explain why the feature is needed, which should be as closely tied to real value as possible. Each one has a clear set of acceptance criteria agreed early on.  And they don't try to pin down the design in detail.

We've found them so useful in trial projects that we intend to use them more widely, on waterfall projects as well as agile ones.  To help us with this, last week we held an internal workshop, with an external consultant who guided us through some of the techniques, pitfalls and implications.  This was really useful.  Our next step will be to decide exactly how to fit this into our methodology; then train the people who will be using it and put it into practice.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…