This document discusses how to communicate agile concepts to a procurement department. It begins by introducing Simon Bates and the digital agency he co-founded, Manifesto Digital. It then defines key agile roles like the product owner and scrum master. The document reviews how an agile contract may define terms differently, like defining user stories, sprints, and the definition of done. It stresses that procurers may not think iteratively so terms need clear explanations. It also notes that agile contracts share risk by allowing flexibility and quick response to issues. Overall, the key points are to define agile roles and terms carefully, explain concepts iteratively, and emphasize how agile contracts can mitigate risks.

1. Simon Bates
How to talk Agile with
a procurement department
28th January 2016

2. 2 / How to talk Agile with a procurement department
Manifesto Digital
We’re an award winning London
based digital agency that loves
ideas, design and technology.
We aim to make people’s lives better, easier, fairer,
more interesting or fun with great strategy, engaging
campaigns and rock solid technology.

3. 3 / How to talk Agile with a procurement department
Simon Bates
• COO and co-founder, Manifesto Digital
• University of Manchester Institute of Science
and Technology Beng Software engineering.
• 17 Years IT experience, working mainly in
web-based technologies and frameworks
• Wrote first Java application in 1997

4. 4 / How to talk Agile with a procurement department
Who are procurement?

5. 5 / How to talk Agile with a procurement department
Procurement are people too…
What you’re taught in procurement
school is quite a ‘widget based’ approach.

6. 6 / How to talk Agile with a procurement department
Scrum

7. 7 / How to talk Agile with a procurement department
Product owner

8. 8 / How to talk Agile with a procurement department
Introduction to Contracts

9. 9 / How to talk Agile with a procurement department
• The only skill you need to understand
a contract is the ability to read
• Defined terms are an important concept to
understand - they can be thought of as like
a sub- routine in a computer program
• Ambiguity is a bad thing - if something’s ambiguous
the contract can be rendered invalid – not always
the case when it comes to proposals!
• Important case law Raffles v Wichelhaus involving
a ship named The Peeless decided in 1864

10. 10 / How to talk Agile with a procurement department
Agile Contracts

11. 11 / How to talk Agile with a procurement department

12. 12 / How to talk Agile with a procurement department
• Our Agile contract runs to 32 pages
• Agile is about each party committing to promise
– agile contracts set these promises out in black white
• Be prepared to have to explain Agile – lawyers/
procurement departments tend not to think that iteratively
• Agile contracts are a contract to collaborate

13. 13 / How to talk Agile with a procurement department
Defined terms

14. 14 / How to talk Agile with a procurement department
Daily Scrum Meeting
A meeting of the Development Team on each Business Day
during the Project Term (except during any period of leave
agreed by the parties) to discuss:
(a) Tasks completed on the previous Business Day;
(b) Tasks to be completed on the current Business Day; and
(c) Any impediments potentially affecting attainment of the
Sprint Goal, including the status of any disputes.

15. 15 / How to talk Agile with a procurement department
Definition of Done
The definition set out in Schedule 2, as amended from
time to time under paragraph 5.5 of the Applicable Terms.

16. 16 / How to talk Agile with a procurement department
Product Backlog
The current version of the document from time to time,
based on the Product Vision and kept up to date by the
Product Owner in accordance with paragraph 4.2
of the Applicable Terms, that comprises:
(a) The Requirements to be completed, sorted in terms
of priority by the Product Owner and any further details
of these Requirements provided by the Product Owner
from time to time under the Statement of Work;
(b) The Results and Delivered Results to date
(c) The estimated business value of each Requirement; and
(d) The Resource Points for each Requirement, determined
in accordance with paragraphs 4.4 and 5.8.2 of the
Applicable Terms From time to time.

17. 17 / How to talk Agile with a procurement department
Initial Product Backlog
The Product Backlog as set out in the
relevant Statement of Work.

18. 18 / How to talk Agile with a procurement department
Product Owner
The person described in Part 3 of Schedule
3 and any replacement from time to time.

19. 19 / How to talk Agile with a procurement department
Plus lots more…
• Development Team
• Resource Points
• Scrum Master
• Sprint Planning Meeting
• Sprint Retrospective Meeting
• Sprint Review Meeting
• User Story

20. 20 / How to talk Agile with a procurement department
The role of risk

21. 21 / How to talk Agile with a procurement department
• Risk costs money
• Agile allows us to share risk
• By committing to an initial backlog and allowing this
to flex, we’re transparent about progress and can
take action quickly to mitigate risks as they arise.

22. 22 / How to talk Agile with a procurement department
Be prepared to explain a lot

23. 23 / How to talk Agile with a procurement department
Don’t think an agile contract
will look any different

24. 24 / How to talk Agile with a procurement department
Ensure procurement are clear
on roles responsibilities

25. Thanks!
Simon Bates
simon.bates@manifesto.co.uk
@simonbates
@manifestovstech