Manifesto for Agile Software Development
Proposes that it may be better to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
While the items on the right are still important the items on the left are more valuable under this philosophy …
1 Comment »
Leave a comment
-
Archives
- December 2009 (8)
- November 2009 (5)
- October 2009 (15)
- September 2009 (12)
- August 2009 (5)
- July 2009 (4)
- June 2009 (7)
- May 2009 (14)
- April 2009 (7)
- March 2009 (7)
- February 2009 (18)
- January 2009 (15)
-
Categories
- analysis
- aspect oriented
- CBSE
- critical system
- design
- digital learning
- e-business
- ecosystem
- final project
- fun
- health informatics
- introduction
- lecture
- maintenance
- method
- oop
- others
- programming
- project
- project management
- quality
- real time system
- requirement
- research
- service computing
- soa
- software architecture
- software developer
- software metrics
- software process
- software product
- software quality
- software standard
- technology
- testing
- tools
- Uncategorized
- webE
-
RSS
Entries RSS
Comments RSS
[...] coba dibuat pada Agile Process Model. Dokumentasi yang lengkap tidak lagi menjadi prioritas (lihat Manifesto for Agile Software Development). Tapi itupun tidak cocok untuk setiap jenis software. Dan hanya developer yang sudah berpengalaman [...]