The Application Development Lifecycle<br />A perspective<br />from someone who<br />has spent 35 years living it<br />
What the business felt it needed<br />
What the business could afford<br />
What the consultant proposed as a compromise<br />
What the business agreed after consulting on the design<br />
The new design after the funding realities hit home<br />
What the detailed spec described<br />
What the project manager would have preferred to deliver<br />
What the programmer was thinking the entire time<br />
How it was documented<br />
The alpha release for user acceptance testing<br />
After fixing faults and including changed user requirements<br />
How the project marketed the rollout<br />
When it was finally delivered<br />
How it performed on the first day<br />
How the users reacted<br />
First year of production<br />
After 5 years of changes and fixes<br />
What the critics said would have happened if THEY had done it<br />
Upcoming SlideShare
Loading in...5
×

The Application Development Lifecycle

400

Published on

...by someone who has spent 35 years living it...

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
400
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

The Application Development Lifecycle

  1. 1. The Application Development Lifecycle<br />A perspective<br />from someone who<br />has spent 35 years living it<br />
  2. 2. What the business felt it needed<br />
  3. 3. What the business could afford<br />
  4. 4. What the consultant proposed as a compromise<br />
  5. 5. What the business agreed after consulting on the design<br />
  6. 6. The new design after the funding realities hit home<br />
  7. 7. What the detailed spec described<br />
  8. 8. What the project manager would have preferred to deliver<br />
  9. 9. What the programmer was thinking the entire time<br />
  10. 10. How it was documented<br />
  11. 11. The alpha release for user acceptance testing<br />
  12. 12. After fixing faults and including changed user requirements<br />
  13. 13. How the project marketed the rollout<br />
  14. 14. When it was finally delivered<br />
  15. 15. How it performed on the first day<br />
  16. 16. How the users reacted<br />
  17. 17. First year of production<br />
  18. 18. After 5 years of changes and fixes<br />
  19. 19. What the critics said would have happened if THEY had done it<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×