• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Failure *Is* an Option
 

Failure *Is* an Option

on

  • 4,677 views

Learning from Failure: Or How IAs Stopped Worrying and Learned to Love the Bombs

Learning from Failure: Or How IAs Stopped Worrying and Learned to Love the Bombs

Statistics

Views

Total Views
4,677
Views on SlideShare
4,652
Embed Views
25

Actions

Likes
10
Downloads
0
Comments
2

4 Embeds 25

http://www.iasummit.org 11
http://xianlandia.com 11
http://www.linkedin.com 2
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Failure *Is* an Option Failure *Is* an Option Presentation Transcript

  • Learning from Failure
    • or… Failure is an Option
    • @ IA Summit 2007
  • What is Failure?
    • The condition or fact of not achieving the desired end or ends.
    • The condition or fact of being insufficient or falling short: a crop failure.
    • Nonperformance of what is requested or expected; omission: failure to report a change of address.
    • A decline in strength or effectiveness.
    • The act or fact of becoming bankrupt or insolvent.
  • Usually…
    • “Success has 100 parents, failure is an orphan”
    • John R Ashton
    • (See also similar quotations from JFK, et al.)
  •  
  • The Case of the Deadly
    • Scope Creep
  • The Project
    • A large software company named after a nearby celestial body
    • A consortium site for developing a proprietary language named after coffee
    • A requirement to automate excruciatingly detailed workflows
    • An opportunity to add community and collaborative features
  • The Assets
    • A 55-page requirements document
    • - 13 unique roles
    • - 90 detailed requirements
    • - Numerous flowcharts
    • The “constitution” of the community
    • The existing site
  • The Discovery
    • Interview multiple stakeholders
      • - Community Participants
      • - Expert Group Representatives
      • - Specification Leads
      • - Executive Committee Representatives
      • - PMO Staff
    • Review of requirements document
    • Analyze analogous, related, and competing sites
    • Present findings and recommendations
  • Results of Discovery
    • Scores of new requirements were “discovered”
    • Examples:
      • Logins should be secure
      • Don’t break old URLs/bookmarks
      • Would like to be able to “impersonate” a user
      • Long wish list of reports
      • Blog, message board, wikis and other community features (later abandoned)
  • Sitemap The Sitemap
  • The Wireframes
  • The Functional Spec
  • The Use Cases
  • In Other Words…
    • Documentation HELL
  • Long Story Short
    • The functional spec was never signed off
    • The prototype was never finished
    • The IA documents were finalized but too late to save the project
    • The cost of the project more than doubled
    • The agency still lost money on the deal
    • The client lost confidence and took the project back in-house
  • Also
    • The site has, nearly a year later, still not re-launched.
  • What I Learned
    • Application sites can’t be built with static site methods
    • Documentation is a double-edged sword
    • Scope creep must be managed forthrightly
  • thank you Christian Crumlish Yahoo! Pattern Detective Director IT/Web Infrastructure, IA Institute