- We believe that agile development builds better software quicker.
(Said better than we could at http://www.agilemanifesto.org/ explained
and with a side order of the user-centricity taught fairly well at
- We believe that web development is a particularly good fit for agile
(Coming from concepts like "permanent beta", "software as a service",
and the idea of webpages as containers for (distributed? widgetised?)
- We believe procurement processes don't let us use agile development
(A process that starts with a feature list rather than objectives and
audiences is a poor fit with agile and user-centric development techniques.)
- We do understand that currrent processes are driven by risk aversion.
(But we think they're arming procurement departments not to lose the
last war, not win the next one. We think producing hugely complex
specifications must be expensive in staff time, we know that responding
to them is. And we think that time is wasted on both sides.)
- And we believe that agile methodologies reduce risk.
(Getting more creativity from more people working on the same problem,
introducing more early points to kill failure, building more
opportunities for change into a project, and delivering more working
software earlier, with more feedback points.)
When we put the session idea up we were pretty conscious that it was a
massive act of hubris to even suggest it - but they say you have to
present at your first camp, and what better than something you're
> My view:
> * Clarify the issues. Both sides write up better versions of what I
> outlined above. Explain and agree on the problem.
> * Start working on what "Agile Procurement" (or whatever we want to
> call it) means. I see it being as simple as some clear bullet point
> rules. Tools used: Wiki and a pub.
> * Promote
> * Profit
> Seem sensible?
> (I know I'm running before I can walk here, but strike while the iron
> is hot etc)
Project director, NeonTribe
Internet user experience designers and programmers
112-114 Magdalen Street, Norwich, NR3 1JD
Sounds like team formation 101...
> the way this is going, happy to play - not sure what we are doing
I agree with the folk who said... Next we need to start fleshing a
process out, and that means a wiki... (Unless anyone knows a slick
online collaborative process diagram making thingy?)
Now - I can drop mediawiki on our dev space easily enough, or we could
use wikia or pbwiki or whatever - or can we get space on the DIUS wiki?
Is Steph here?
> Awesomes. I'm there. Got a location? You thinking office or pub?
> 9-11, 10-12, 4-6?
10-12 best for me.
> - WTF do we mean by agile procurement (scope of types of services
> involved, process we'd recommend at a high level...)
> - Who TF do we need to include/target (government, non-government,
> suppliers, commissioners, OJEU, Catalyst/OGC...)
> - When TF would we like to target running an event to bring in this
> wider group including Tom W (who has confirmed he'd come along to a
> clearly scoped session)
- WTF are the objectives and agenda of that event.