Rob Harr
RUNNING AWESOME
DISCOVERY PROJECTS
@robertharr
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
#DaytonStrong
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
We are hiring!
https://seesparkbox.com/jobs
Tangent!
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
YMMV!
Slide 8
Slide 8 text
Websites are software.
Slide 9
Slide 9 text
Determining scope on software
projects at the beginning is
irresponsible and impossible.
Slide 10
Slide 10 text
Reason 1:
Determining scope on
software projects upfront is
impossible because:
Clients are really bad at describing
their actual needs.
Slide 11
Slide 11 text
We are bad at estimating work
because we are optimistic.
Reason 1:
Reason 2:
Determining scope on
software projects upfront is
impossible because:
Clients are really bad at describing
their actual needs.
Slide 12
Slide 12 text
We are bad at estimating work
because we are optimistic.
Reason 1:
Reason 2:
Determining scope on
software projects upfront is
impossible because:
Clients are really bad at describing
their actual needs.
Business needs change over time.
Reason 3:
Slide 13
Slide 13 text
Project don’t fail for technical or
design reasons, they fail because of
the people involved.
Slide 14
Slide 14 text
I believe the biggest risk for
software projects is building the
wrong thing.
Life is too short to work with people
you hate.
Rob’s two basic rules for
happiness in business:
Rule 1:
Slide 116
Slide 116 text
If you ever become annoyed by a
client, it is only because you’re not
charging them enough money.
Life is too short to work with people
you hate.
Rob’s two basic rules for
happiness in business:
Rule 1:
Rule 2: