This document discusses an iterative approach to digital product development using agile principles. It advocates taking a product-based rather than project-based approach, with continuous quality improvement and refinement of the product over time based on feedback. Agile practices like having very structured but flexible processes, visual transparency, and failing fast are recommended. While agile has risks if not implemented properly, following principles like minimum viable products and iterative design allows products to be informed by measurement and to evolve as needed.

1. An iterative approach to
digital product development

2. comfort zone
1

5. Movement
Time !!

6. Introduction
2

7. Introduction
• The digital environment is fluid and changes
rapidly, demanding the ability to respond to
change and feedback in short time frames
• Taking a purely project based approach to
your digital products can inhibit creative
opportunism and responsiveness

8. Projects ….
Things change
• they always do
• they always will
You’re not in control of that
its about how you can respond
This is often a change in attitude and culture

9. Product over project
• Projects end
• Products remain
• Projects try and cram it all in
• Products grow over time

10. Continuous quality improvement
• Digital products are constantly evaluated and
improved based on efficiency, effectiveness
and value
• Challenge the final outcome if there is one
• Refine and improve return on investment

11. Agile – quick intro
3

12. • quick and dirty
• taking short cuts
• being undisciplined
• just having a wall
• change at will
• for cowpersons
Agile is not -

13. Agile is -
• very structured
• very disciplined
• gives you control
• a discipline
• change ready
• fast paced

14. Agile makes things obvious
• it’s very visual
• transparency
• shows scope creep
• self reflection
• expectation issues

15. Being able to…
• Fail sooner than later
• See issues quickly
• Transfer ownership of decisions away from
implementation units
• Increase output
• Understand capacity and cost

16. Agile has risks
• in word only
• without review cycle
• as an excuse
• cowgirls/cowboys

17. a beautiful alignment
4

18. Product based planning
• Product based planning is the fundamental
planning technique that supports Prince 2 and
MSP
• Has four key parts
– Project product description
– Product breakdown structures
– Product descriptions
– Product flow

19. Project product description
• Purpose: Scope and requirements
• Composition: Key outputs
• Customers expectations
• Assumptions

20. Agile and Prince 2 – a lovely match
• They can work together
• PBS – it’s perfect
• Stories - Scope
• Business value – key outputs
• Acceptance criteria – quality criteria

21. Iterative design
5

22. Iterative design
• We don't know everything upfront
• Things change they always do
• Products informed by measurement
• Only do what you need now
• Allow for end goal to be reviewed & refocused

32. MVP – minimum viable product
• Begin with what is needed now
• Release often
• Allow for growth
• Defer decisions until appropriate time
• Getting traction

33. The design space
• Creative thinking
• Outside the box
• Understanding and having boundaries
• Blue sky vs reality

54. formalising it all
6

62. Questions and
workshop time....
7

63. In your own work environment
What would
inhibit you from
employing a
more agile
attitude ?
barriers opportunities
What
opportunities
are there to
employ a more
agile attitude ?