means that that it is better to complete 9 out of 10 parts of an iteration with deliverable, testable, features, than it is to bring all 10 parts to a level of 95%, with no deliverable, testable features.
One works at the completion of the tenth, making whatever adjustments necessary to bring it to 100% completion.
In success-oriented programming, the celebration of each success brings new energy and experience to the team in the form of discoveries of what it takes to make sure ItWorks
. While it may be disappointing to have to LetOneGo
so that success can be arrived at on the nine deliveries, it is also true that the success releases resources to concentrate upon the final task.
Of course, no account of Success Oriented Programming (SOP) would be complete without comparison to:
- FOP - Failure Oriented Programming - The endurance of each catastrophe brings new despondency and inadequacy to the team in the form of discoveries of what it takes to make sure ItDoesNotWork.
- POP - Peer Oriented Programming - Each line of code is written by the programmer to the left of you. By arranging the team in a circle, productivity can be increased exponentially without actually doing any work.
- BOP - Beer Oriented Programming - Celebrate success first, then celebrate celebrating success, then celebrate celebrating celebrating, then celbrate shuccess AGAIN, then shelbrate shucchesh *urp* Phrogramming ish whash? ONE MORE *hic* TIME! goddamn I love you guysh, *sniff* I really *urp* do. *CRASH*
Now you'll have to 'scuse me, 'cause I gotta LetOneGo
, er, release resources, and it'd be rude to do it in public.
I thought FOP was Fear Oriented Programming, which is generally the outcome of ManagementByKickingAss....
means something far more bodily in the UK.