Deeson Solutions Architect Steve Coppin-Smith focuses on scrum in an agency environment. In his talk he explaines what scrum is, why is it relevant to web development, and how can it help coders.

1. Scrum Agency
Scrum-but for agency-client relationships
www.deeson.co.uk

2. A little intro...

3. OK, great. So what’s
Scrum?

4. Single project focus
7 +/- 2 team members
Highly available
product owners
Scrum is likely to work
well when you have
Multiple projects
3 +/- 1 team members
Highly illusive product
owners
Scrum is considerably
less likely to work well
when you have

5. Why bother?

6. We know Scrum to:
Be highly efficient
Be great value
Maintain an effective pace
We want to:
Exceed our client’s expectations
Work on exciting projects
Have fun doing it!

7. To do that we will:
1. Find a solution using Scrum
2. Find a solution within Agile
3. Find something else
4. Make something up

8. Pitching Scrum
Help us to help you!

9. We would like a CMS, that meets our goals,
that integrates with a CRM, with content
migrated from our current system.
Pitching Scrum
How much will that be?

10. So how about we implement an iterative
process whereby we can learn together about
your goals and deliver early versions you can
test with real users.
Pitching Scrum
Sounds great!

11. Pitching Scrum
How much will that be?
And what exactly do we get?

12. Pitching Scrum
PRODUCTION

13. Pitching Scrum
PRODUCTION

14. Pitching Scrum
WORKSHOP
DISCOVERY PRODUCTION

15. Practicing Scrum

16. Multiple Projects

17. … means multiple variants.
Multiple projects
TASK #1
TASK #2
TASK #3
TASK #4
TASK #5
TASK #6
TASK #...
TASK #1
TASK #2
TASK #3
TASK #4
TASK #5
TASK #6
TASK #...
TASK #1
TASK #2
TASK #3
TASK #4
TASK #5
TASK #6
TASK #...
TASK #1
TASK #2
TASK #3
TASK #4
TASK #5
TASK #6
TASK #...
PROJECT A PROJECT B PROJECT C PROJECT D

18. 3 +/- 1 team members

19. … so communication is key!
3 +/- 1 team members

20. Highly illusive product
owners

21. Sprint reviews
Gathering priorities
“Scrum masters”
Highly illusive product owners

22. Something I couldn’t find
a good place for

23. Planning Poker

24. Estimate variance was high
Estimated solution lived in
one person’s head
Team felt duped by
inaccurate estimates
Let’s say, hypothetically,
there was one person
estimating
Estimate variance reduced
Requirement is better
understood
Team co-owns the estimate
But it’s ok, because they
replaced it with Planning
Poker!
Best supporting Scrum
practice in an agency
environment

25. So, is it working?

26. We are:
Meeting our estimates
Providing higher quality solutions
More organised and flexible
Our clients are:
Happy
Successful
Coming back for more!

27. Got any good ideas?
@steve_coppin | stevec@deeson.co.uk
www.deeson.co.uk