September 6, 2013

Agile Prototyping to Confirm Requirements

By Russ Lewis. Published online September 6, 2013

Delivering Value Early

This post nails the value to customers of rapid, or agile prototyping. We first met the charming people at MECA on Tuesday afternoon, so we could hear directly what they wanted from their new information system.

Why did we want to meet with them when we had a (very clear) 250 page RFP document?

Because face to face communication is far better than any other form. People communicate with their whole being; they nod in agreement, and show excitement when they "get it". Significantly, they display hesitation or confusion when something is unclear and that allows us to repeat or ask questions.

First Features Go-Live Tomorrow

I'm writing this at midnight on Wednesday evening and the team will invite the first users onto the sites tomorrow so they can give us feedback on the structure and layout. Let me put this in another way:

We have done a significant piece of work, and if the client is satisfied with it, they will start using it on Thursday.

What Did We Really Do?

This is quite shocking to people until they start experiencing the benefits of Agile methods, so some explanation is required. This is the background, steps taken, and what will be delivered:

  • No development work was done before the meeting, but there had been three days of reading the documents and discussion within the team.
  • We created, estimated and prioritized  a set of tasks that would need to be performed
  • One of those tasks was to produce a demonstration
  • The platform had been selected (SharePoint), so an online SharePoint farm was provisioned in readiness. This was built from scripts and took about 30 hours. The build was started late on Tuesday afternoon.
  • As the solution architect, I implemented my first draft design of the site collections, portals, sites, and sub-sites. I customized a few of the home pages to show the specified site names.
  • There is nothing like "on the job" training, so one member of the team, who is new to SharePoint, worked together with me, until he was comfortable enough to take over the task of creating the menus and site navigation.

This early phase of work is really important because it tests the architecture, implements the stated requirement, and allows the client to see if what they asked for is actually what they want!

Until the client has approved this or a proof of concept, it is not worth investing in any more development, because the cost of making changes rises very rapidly once the site architecture is in place. However, you cannot design that architecture without building and testing it, which is the very nature of Agile – understand, build, test, refine, understand more, build more, test more, repeat until done.​

Delivering Packets of "Done"

The overall project we are tendering for may take 12 months or more to develop, and skill that successful Agile practitioners develop is to divide larger components into their smallest units of functionality and value to the business.

Tomorrow, we will deliver the following:

  • Overall site structure showing navigation between business areas and sites
  • Public internet website with home page and live blog
  • Web Portal intranet site with authentication for two (real) users
  • Three directorate sites with test users from each, all with appropriate access rights
  • Extranet site for partners and consultants with one test user
  • A process for deploying the application

Benefits to the Client​

The only working functionality here is the blog, so what are the benefits to the business?

  • Users can start getting used to the new system – early adopters and champions emerge
  • Builds interest and buy-in for users – who actually see something happening quickly
  • Proof of design – reduces risk of doing more work on something that turns out to be wrong
  • Proof of architecture – better to discover early if users can access the site
  • Proof of performance – and get an idea of the performance doing something real
  • Proof that the development team can deliver to a forecast – builds confidence and trust
  • Business can prioritise the next feature for development

That's about it for this blog post, so all I need to do is publish it to that shiny new SharePoint farm of ours.

Newsletter signup

    Recent Posts

    Ways of Working: 5 improvements for leaders

    Most ways of working still rely on functional hierarchy, where managers make decisions and workers do the work. Managers know they can't change this work structure, but they can transform its effectiveness without asking for permission and without needing a budget. Before exploring the changes that transform the way people work, we need to recognise […]

    Read More
    Manage tensions if you want an agile transformation

    Today’s challenge is that traditional management approaches, where managers tell people what to do and how to do it, are not as effective as they once were. Agile transformation takes years, but changing management’s focus from people to tensions could be a better solution. It is simpler, faster, and considerably more cost-effective. Management is the […]

    Read More
    Collaboration versus simplification for organisational change

    One of my favourite books on organisational change is ‘Who Moved my Cheese?’ It’s short, and mice looking for cheese to eat is an appealing analogy. It’s a model for managers because it covers four theoretical outcomes of change. Those outcomes are: what happens if I (or we) do, or don’t make this change, what […]

    Read More
    12 signs that using 'ambidexterity as an agile transformation model' is not my original idea

    You see, I thought I was the first agilist to make the connection between agile transformation models and organizational ambidexterity. Certainly, it seemed original when it emerged in conversation with my supervisor. In fact, it was Dr Alireza Javanmardi Kashan’s idea (better make it 13 signs), but it came from our conversation so we said […]

    Read More
    What is contextual ambidexterity?

    Contextual ambidexterity is a culture that expects exceptional performance in both innovation and operation, overturning the illusion that it is either/or. Contextual ambidexterity is agile for managers.

    Read More
    The Future of Agile Leadership

    Introduction The future of leadership is Agile There are many different types of leadership styles and not all work well in every situation. The most popular method, the "Command and Control" style which has been dominant for centuries, may be on its way out as research shows that this type of leadership does not foster […]

    Read More
    February 21, 2021
    Agile Delivery is a challenge for organisations like yours

    Achieving Agile Delivery is the toughest challenge of an executive career, no matter if it’s called digital transformation, adoption, or DevOps. The reality behind the highly-polished powerpoint decks and magazine stories is that despite fortunes being spent over many years, Agile is ‘out of reach’ to many leaders and managers. The evidence shows that challenges remain unresolved in many […]

    Read More
    April 20, 2014
    How Agile Defeated Goliath

    Malcolm Gladwell tells the story of David and Goliath as an unfair contest with odds stacked against the giant. Shepherd David with his simple but precise sling shot isn’t the bravest of King Saul’s men but the one who recognises the deadly disadvantage of an unwieldy, heavily armour-clad, sword-bearing infantryman in one-on-one combat. Gladwell is […]

    Read More
    June 18, 2014
    Developing Skills the Agile Way

    Development Occurs over Time, not on a Training Course During our many combined years as trainers with Learning Tree International, the average instructor grade exceeded 3.8 of a possible 4.0. Attendees loved the training, and provided fantastic testimonials. But that doesn't mean they used what we taught them, or that they improved because of the […]

    Read More
    1 2 3 11
    linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram