The document provides examples of tools and templates that can be used to plan an agile project launch, referred to as an "Inception Deck". It includes: 1. Why We Are Here - Outlines the purpose and objectives of the project. 2. What Can You Expect - Describes the project approach, timeline, resources needed. 3. What Are We Being Asked To Do - Identifies assumptions, risks, and next steps to establish shared understanding. The examples cover topics such as benefits, stakeholders, estimates, constraints, and tests to set the project up for success.

1. Launching
Agile Projects
Examples
Simon Girvan
@simongirvan
A summary of all the examples from the workshop

2. Elevator Pitch Example
For Pirates
who Need a new or additional parrot
the ‘Parrots Arrr Us’ Website
is a Pirate and Parrot matching service
that finds a parrot to perfectly match your needs
Unlike stealing one from another pirate
Our Product removes the risk of revenge attacks or a bad bird
‘Parrots Arrr
Us’ example

3. Product Box
• Benefits not features
• Emotions and feelings

4. Our ‘Why Are We Here’
• On a personal level, we want to develop ourselves
• We want to reach Certified Team Coach® level with Scrum Alliance
• Running workshops and facilitating large groups is good evidence
• This is a good professional challenge for us both
• We are passionate about sharing our experiences and want others to
get good results from these approaches too
• The submission has been accepted, so it will definitely go ahead (low
risk of being cancelled)
Conference
workshop
example

5. Our ‘Elevator Pitch’ 1
For people at this Agile conference
who want to learn new techniques and how to apply them
the Launching Agile Projects Workshop
is an interactive and informative workshop
that is hands-on, fun and useful
Unlike other ways to learn
Our Product allows participants to immerse themselves in the
material, embedding the learning more effectively
Conference
workshop
example

6. Our ‘Elevator Pitch’ 2
For people at this Agile conference
who want to learn new techniques and how to apply them
the Launching Agile Projects Approach
is a way of preparing for the start of a project
that helps teams get sufficient knowledge to start a project
Unlike other project start-up techniques
Our Product is a lightweight approach that uses a just enough, just
in time philosophy
Conference
workshop
example

7. Our ‘Product Box’

8. In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
• Full Coverage of both Inception
Deck
• Limited coverage of LiftOff and
Chartering
• Exercises and Practical content
• Templates and Hand Outs
• Meaningful Examples
• Rehearse with at least one group
• Materials can be reused for other
events
• Exercises for all elements
• Feedback from every group
• Detailed discussion of each
element
• How to deal with detailed questions during the main sections
• Downloadable Resources?
• How far to go down the pirate route wrt costume, etc
Conference
workshop
example

9. Meet The Neighbours
Generic
example

10. Our ‘Meet The Neighbours’
Conference
workshop
example

11. Our Assumption MapOur Assumption MapOur Assumption Map
Assumption Map
Have
Evidence
Brainstorm all your assumptions and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based on ideas from @davidjbland, @danto_ma and @AlexOsterwalder.
There is
demand for this
workshop
Technique
has merit
Technique
is portable
Workshop
format is good
enough for
learning
Room
layout is
suitable
Exercise
choices are
suitable
People haven’t
heard much of
this before
Weighting
between ID
and LO is
OK
Weighting
between
content and
exercises is OK
Two presenters
are better than
one
Timeslot allocated
is conducive to the
workshop format
Pirate theme is
appropriate
Conference
workshop
example

12. Our ‘Candidate Solution’
Conference
workshop
example

13. Candidate Solution
‘Parrots Arrr
Us’ example

14. 1.Fittingineverythingwewantinthe
timethatwehave
2.Havingenoughtimetoprepare
3.Willtheexercisesbeuseful?
4.Willpeopleactuallytakepartinthe
exercises
5.IsthesplitrightbetweentheInception
DeckandLiftoff?
AwakeList
Thesearethethingsweareareworriedmay
keepusawakeatnight
Whatarethethingsthatyoupersonallyareworryingabout?Thisismorethanjustproject
risks.Includenon-technicalfactorslikepeople,facilities,processes,skills,otherdemands
onyourtime,officepolitics,etc.Discussamongsttheteamwhatyoucandoaboutthem.
@simongirvan
Conference
workshop
example

15. Our ‘Wheel of Pain’
We are not based in same location so plan
at least 2 workshops where we can work
together. Use online collaboration tools.
There is a lot of information to try to get
across. Use pilot groups to test format.
Create templates and handouts to help
attendees remember the content.
Conference
workshop
example

16. Our ‘Choose Your Approach’
• Adhoc planning approach
• Collaborative online and in person
• Iterative – low detail to start
• Keep actions in Teams
• Content on Sharepoint
• No formal reporting
Conference
workshop
example

17. Choose Your Approach
How will we manage and
govern the project?
How will we
communicate with
stakeholders?
• Agile using Scrum
• 2 week Sprints
• Visible Backlog
• MMP as first release as early as
possible• All stakeholders invited to
Review/Demo• Real users from version 1 onwards
• Monthly update to Board
Generic
example

18. How Big Is This Ship? (Size It Up)
• Best guess rough estimate of size and duration
• Initial estimate of the team required to do this
Sprint 0
2 Senior Engineers
0.5 Infrastructure
MMP
Development
Standard Agile team
including BA, UX and
Architecture experience
Releases 2-n
Standard Agile team, including higher
level devops and test experience
2 Weeks 4 – 6 weeks
8 – 12 weeks
Start Developing in 2 weeks
MMP 4 – 6 weeks later
4-6 further versions
Team size 2-7
ROM Cost £180-£270k
ROM Duration 3 – 5 months
Generic
example

19. Our ‘How Big Is This Ship?’
Inception Deck
Good Enough for
Rehearsal
Include reviewers and
pilot workshop attendees
By end Jan 2019 By end Feb 2019 By end March
4 months duration
17 days effort (8.5 each)
Less than £100
First
Rehearsal
Revise and
more rehearsal
Prep &
Deliver
Preferably at least
one more
runthrough
Order print
materials
During April 10 May
2019
Conference
workshop
example

20. What’s Gonna Give? Decide the extent to which you expect each factor to
be flexible or fixed.
If too many are too fixed, consider forcing a minimum
number of points (say 10 if scoring 4 factors)
@simongirvan
Deliver All
The Features
Based on an idea from “The Agile Samurai” by Jonathan Rasmusson
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
Stay On
Budget
Can be flexible
on this
Must do
this
Deliver on
Time
Deliver High
Quality
Others may include Useability, Security, Supportability, Accessibility, etc. If they matter to you or your stakeholders include them!
Must
Must
Must
Must
Must
Must
Clarity of
Message
Portable
Ongoing
Support
Conference
workshop
example

21. Our ‘Final Test’
We do we know enough about this
project:
• We know what’s required to have enough
material available to present;
• We know how we intend to test it;
• We know what the first steps are.
We are ready to start!
Conference
workshop
example

22. Summary of the Inception Deck
• Why Are We Here:
• Why are we here?
• Elevator Pitch
• Product Box
What Can You Expect?
• Choose Your Approach
• Size it Up
• What’s Gonna Give?
• The Final Test
What Are We Being Asked To Do?
• The NOT List
• Meet The Neighbours
• Assumption Map
• Candidate Solution
• Awake List
• Wheel of Pain
In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake ListThese are the things we are are worried may
keep us awake at night
What are the thing
s that you personally are worrying
abou
t? This
is more
than
just proje
ct risks. Inclu
de non-technical
facto
rs like peop
le, facilities,
processes,
skills
, other demands
on your
time, office politics, etc. Discuss amongst
the
team
what
you can do abou
t them
.
@sim
ongirvan
Based
on ideas
from
“The
Agile
Samu
rai”, by Jonat
han Rasm
ussan
What’s Gonna Give?
Decide the
extent to which
you expect each factor to
be flexible or fixe
d.
If too
many are
too
fixe
d, consider forcing a minim
um
number of points (say 10 if sco
ring 4 factors)
@simongirvan
Deliver All
The Features
Bas
ed on an idea from
“Th
e Agile Sam
urai” by Jon
athan Ras
musso
n
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
Stay On
Budget
Can be
flexib
le
on
this
Mu
st do
this
Deliver on
Time
Deliver High
Quality
Oth
ers
may include Use
ability,
Sec
urity, Sup
portability, Acc
essibility, etc. If they matter
to you
or you
r stakeh
olders
include them!
Mu
st
Mu
st
Mu
st
Mu
st
Mu
st
Mu
st
Assumption Map
Have
Evidence
Brains
torm all your assum
ptions
and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based
on ideas from by @david
jbland,
@danto
_ma and @AlexO
sterwa
lder.

23. The Journey

25. The first choice for pirates across
the seven seas
• We will understand what our customers need and develop our
services to meet a growing range of pirate needs, starting with
parrots.
• We will make the “Parrots Arrrr Us” website the first port of call for
pirates everywhere.
• We will make the “Parrots Arrrr Us” website accessible for pirates
with disabilities.
• We will be easy for our suppliers to do business with
Vision and Team Mission Examples ‘Parrots Arrr
Us’ example

26. Mission Tests Example
• The first version of the Parrots Arrrr Us website is
accessible from each of the seven seas.
• By 6 months parrots can be delivered to each of the 7
seas.
• The first version of the website is usable by Pirates with
one hook arm and one eye patch.
• By 6 months, the website is fully accessible to
international standards (WCAG 2.0)
• By 9 months, at least one additional product or service has
been launched.
‘Parrots Arrr
Us’ example

27. Alignment
Exercises and Artefacts that help the
team understand each other, and how
they can each make their maximum
contribution to the project

28. Simple Rules Example
1. Integrity - We do what we say we will do
2. Ingenuity - We collaborate to help us come up with the
best ideas
3. Impact - We focus on delivering value to the customer in
everything we do
4. Teamwork - We look out for each other and always offer to
help
Simple Rules
These are the things we value and believe in
A few (5 plus or minus 2) short descriptions of the values and beliefs that the team find important.
Start with an action verb. Eg: “Ingenuity - We collaborate to help us come up with the best ideas.” @simongirvan
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
Generic
example

29. Working Agreement Example
Generic
example1. We don’t work on anything that isn’t on the Sprint Backlog
2. Our calendars are always up to date with location and
availability
3. All our meetings matter - No meeting purpose; no meeting
4. We have fun and don’t take ourselves too seriously
5. We respect each other’s quiet time - Headphones on means
no interruptions.
Working Agreement
These few (5 plus or minus 2) statements describe the contract between the team members. They describe specific
actions that the team have decided are important to them and will call each other out on. They will evolve with the team.
For example: “We respect each other’s quiet time - headphones on means no interruptions” @simongirvan
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
As a team, we work together best when…

30. Context
Assumption Map
Have
Evidence
Brains
torm all your assum
ptions
and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based
on ideas from by @david
jbland,
@danto
_ma and @AlexO
sterwa
lder.
Exercises and Artefacts that help the
team understand the external
environment and what they require of
others in order to succeed.

31. Context Diagram
‘Parrots Arrr
Us’ example

32. CommittedResources
Thesearetheresourcesthattheteamneedor
wanttohelpthemdelivertheproduct
Consideranythingthatmakesadifferencetotheteam’sabilitytodeliver.EgIT
resources,licences,training,accommodation,budgets,tools,time,availability
tostakeholders,hardware,etc
@simongirvan
Basedonideasfrom“Liftoff”,byDianaLarsonandAinsleyNies
CommittedResourcePriority
(M/S/C)
✔AWSHostingandstorageM
✔TravelBudgetM
✔StationaryBudgetM
TrainingS
✔SoftwareLicenceUpgradesC
ConferenceAttendanceC
4kMonitorsC
✔AccesstoendusersS
AllStakeholdersatSprintReviewsS
OfficeCoffeeMachineC
ElectronicWhiteboardC
Generic
example

33. Prospective Analysis Imagine all the possible events that could happen over
the next few months, both positive and negative.
Assess their impact (positive and negative) on the
project and the likelihood of them happening. Be bold.
@simongirvanProbability
Won’t Happen
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
Unlikely 50/50 Chance Likely Will Happen
Impact
-3
-2
-1
0
3
2
1 Website V1 live
on June 1
Livestock license
rejected
First Successful
Order
Completed by
15 June
Process
orders from
Region 1
Delivery to all 7
seas available
Approval for
next project
idea
Problems
delivering to
certain areas
Full seven seas
service available
in version 1
Competitor will
launch before
we do
Idea is copied
by competitor
‘Parrots Arrr
Us’ example