7. I had a client a couple of months ago call
me at 6:30 in the morning yelling and
screaming because his site had been down
for over an hour. I drag myself out of bed,
get to the computer and his site comes
right up... I told him to try to get on
Google. Guess what? According to him
Google was down too. I politely told him to
call his internet provider because that was
down and once his internet came back up
to use it to search for a new developer.
Saturday, June 29, 13
8. I had a project that had multiple
decision makers. They wouldn't
move forward unless they all agreed
on any one point. And they couldn't
agree on anything.
Saturday, June 29, 13
9. Drunk guy: "Oh, you make sites?
Let's make something like Facebook
and earn alot of money! I'll come up
with ideas and you make it.”
Me: “Got any suggestions?”
Drunk guy: “Yeah, we need
something like Facebook so we'll be
rich! You go make it!"
Saturday, June 29, 13
10. The client doesn't know what they want,
so they spend endless hours in meetings
with you "throwing ideas around". Then,
despite the warnings that they were
consuming their contracted hours in this
fashion, insist that they shouldn't have
to pay for the time because the site still
hasn't been built.
Saturday, June 29, 13
11. make for nightmares for
us, our partners (internal
and external),They bring
us to an Open Sourced
“Arkham”... and we feel...
Lack of Planning
Lack of Communication
Lack of Process
Lack of Focus
Differences in CULTURE
Saturday, June 29, 13
12. make for nightmares for
us, our partners (internal
and external),They bring
us to an Open Sourced
“Arkham”... and we feel...
Saturday, June 29, 13
20. Cowboy or Extreme
• Highly informal
• Focuses on Stakeholders
• Can be used in very unpredictable projects
• Can be excellent for rapid prototyping
Roy Montgomery
on flickr
Saturday, June 29, 13
31. Project Management
Acts as Scrum Master
Leads Pointing Stories
Protects Dev Team from Distractions During
Coding
Ensures that the Team Doesn’t Make Mistakes
Manages the Schedule
Saturday, June 29, 13
32. Product or UX
Owns Backlog
Personas, Epics, and Stories
Answers questions that Clarify Business Needs
Demos Software at the End of Sprint
Saturday, June 29, 13
33. Developers
Self Organizes Selected Stories
Decides What Can/Can’t be Completed in
the Timebox
DEFINES the Implementation of
Business Needs
Executes
Saturday, June 29, 13
34. This Next Model Works Well
For Projects with a Long
Timeline
Saturday, June 29, 13
35. A Sample Timebox Timeline
60 days - Business Requirements
40 days - User Stories, Wireframes,
Comps
20 days - Beginning of Current
Development cycle
Saturday, June 29, 13