Agile Commissioning What’s  that ??
Caveat <ul><li>This is not an attempt to explain a new set of procurement rules </li></ul><ul><ul><li>For that, go to plac...
Things Valued <ul><li>Individuals and interactions   over processes and tools  </li></ul><ul><li>Working software   over c...
Principles <ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable softw...
Why bother? (+ve) <ul><li>Collaborative working is the order of the day </li></ul>With thanks to the Ontario Gov’t archive...
Why bother (–ve) <ul><li>“ When it comes to Web 2.0, by the time the [organisation] has established a programme board, hir...
Context 1 ?!?? !!!!
Context 2 <ul><li>“ New concepts can be prototyped in less time than the meeting you’d have needed to discuss it in the fi...
My Context
Maybe need to think about this a bit?
Think 1 ‘what’s the Pitch?’ <ul><li>Knowing what you think: pitching as a design tool </li></ul><ul><ul><li>what is the im...
Think 2 - Commissioning as the corollary of development <ul><li>Have a look at the Agile Software Development page on wiki...
Where & when might this be useful? <ul><li>[ this isn’t a one-size-fits-all approach] </li></ul><ul><li>? </li></ul><ul><l...
Discourse available? <ul><li>…on Agile Procurement at Google Groups </li></ul><ul><li>http://groups.google.co.uk/group/agi...
Upcoming SlideShare
Loading in …5
×

Agile Commissioning A Beginners View

694 views

Published on

I collated this simply as a conversation starter at the Scottish Public Sector Barcamp on 27-03-09. In the event I didn't get the opportunity and so was able to put the material 'in the bank' for another time. But on reflection it seemed silly not to make it available anyway - you can do your own voice-over!

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
694
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Agile Commissioning A Beginners View

    1. 1. Agile Commissioning What’s that ??
    2. 2. Caveat <ul><li>This is not an attempt to explain a new set of procurement rules </li></ul><ul><ul><li>For that, go to places like </li></ul></ul><ul><ul><li>NESTA or the OGC </li></ul></ul><ul><li>It’s more about how you need to begin to think in this context – your mental framework </li></ul><ul><li>First, we need to describe how we want to go about doing what we want to do (!) </li></ul>
    3. 3. Things Valued <ul><li>Individuals and interactions   over processes and tools  </li></ul><ul><li>Working software   over comprehensive documentation   </li></ul><ul><li>Customer collaboration   over contract negotiation   </li></ul><ul><li>Responding to change   over following a plan   </li></ul><ul><li>Manifesto for Agile Software Development </li></ul><ul><li>http://agilemanifesto.org/ </li></ul>
    4. 4. Principles <ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. </li></ul><ul><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. </li></ul><ul><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. </li></ul><ul><li>Business people and developers must work together daily throughout the project. </li></ul><ul><li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. </li></ul><ul><li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. </li></ul><ul><li>Working software is the primary measure of progress. </li></ul><ul><li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. </li></ul><ul><li>Continuous attention to technical excellence and good design enhances agility. </li></ul><ul><li>Simplicity--the art of maximizing the amount of work not done--is essential. </li></ul><ul><li>The best architectures, requirements, and designs emerge from self-organizing teams. </li></ul><ul><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. </li></ul><ul><li>Manifesto for Agile Software Development </li></ul>
    5. 5. Why bother? (+ve) <ul><li>Collaborative working is the order of the day </li></ul>With thanks to the Ontario Gov’t archives at http://www.archives.gov.on.ca/english/exhibits/diaries/bigs/big_39b_barn-raising.htm
    6. 6. Why bother (–ve) <ul><li>“ When it comes to Web 2.0, by the time the [organisation] has established a programme board, hired a management consultant, logged the issues, mitigated the risks and approved the Project Initiation Document, users will have got bored and moved elsewhere.” </li></ul><ul><li>Web 2.0 in Local Government: Are We Ready To Lose Control? </li></ul><ul><li>Stephen Hilton </li></ul><ul><li>http:// www.headstar.com/egblive/?p =195#more-195 </li></ul>
    7. 7. Context 1 ?!?? !!!!
    8. 8. Context 2 <ul><li>“ New concepts can be prototyped in less time than the meeting you’d have needed to discuss it in the first place” </li></ul><ul><li>Simon Willison, at the launch of the Guardian’s ‘Open Platform’ (11.03.09) </li></ul>
    9. 9. My Context
    10. 10. Maybe need to think about this a bit?
    11. 11. Think 1 ‘what’s the Pitch?’ <ul><li>Knowing what you think: pitching as a design tool </li></ul><ul><ul><li>what is the important need that you aim to meet? </li></ul></ul><ul><ul><li>what is your approach ? </li></ul></ul><ul><ul><li>what are the quantifiable benefits from your approach? </li></ul></ul><ul><ul><li>what’s the competition ? </li></ul></ul><ul><li>Boyd, F. (2007) How does innovation happen? Published by Creativity East Midlands for the Creativity: Innovation and Industry conference, 6th December 2007 </li></ul><ul><li>http://www.cii.dmu.ac.uk/resources/frank/ Boyd .pdf </li></ul>
    12. 12. Think 2 - Commissioning as the corollary of development <ul><li>Have a look at the Agile Software Development page on wikipedia </li></ul><ul><ul><li>And do a mental search & replace with ‘commissioning’ </li></ul></ul><ul><ul><ul><li>Connection with Agile Manifesto </li></ul></ul></ul><ul><ul><ul><li>Useful points on </li></ul></ul></ul><ul><ul><ul><ul><li>Comparisons with other methods e.g. waterfall, cowboy coding etc. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Suitability of the approach in different project contexts </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Appropriate project management tools etc. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>http://en.wikipedia.org/wiki/Agile_software_development </li></ul></ul></ul></ul>
    13. 13. Where & when might this be useful? <ul><li>[ this isn’t a one-size-fits-all approach] </li></ul><ul><li>? </li></ul><ul><li>? </li></ul><ul><li>? </li></ul><ul><li>The point is that you need to think about it not just move from one ‘answer’ to another one… </li></ul>
    14. 14. Discourse available? <ul><li>…on Agile Procurement at Google Groups </li></ul><ul><li>http://groups.google.co.uk/group/agile-procurement?pli=1 </li></ul>

    ×