Agile: verschil tussen versies
Uit Petities
(nav kritiek op EU en eParticipatie blog http://pep-net.eu/blog/2011/07/28/scratching-where-it-doesnt-itch-time-to-talk-about-eparticipation-and-elephants/) |
(responding to change) |
||
| Regel 6: | Regel 6: | ||
:'''Responding to change''' over following a plan | :'''Responding to change''' over following a plan | ||
| − | In practise, the [[helpdesk]] treats every e-mail from an end-user carefully as a request for further developments. The documentation is pragmatic and basic, the contract with the company that developed the code was based on collaboration on a rough set of features which should eventually work, rather than detailed descriptions. Development on the code continued beyond the contract requirements, for example when the actual usage of the website required it. | + | In practise, the [[helpdesk]] treats every e-mail from an end-user carefully as a request for further developments. The documentation is pragmatic and basic, the contract with the company that developed the code was based on collaboration on a rough set of features which should eventually work, rather than detailed descriptions. Development on the code continued beyond the contract requirements, for example when the actual usage of the website required it. Plans are being adapated to changes continuously, rather than where a plan first gets implemented and then evaluated. |
[[Category:developer]][[Category:geschiedenis]] | [[Category:developer]][[Category:geschiedenis]] | ||
Huidige versie van 14 aug 2011 om 10:01
Petities.nl is developed according to the principles of the Agile Manifesto on software development:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
In practise, the helpdesk treats every e-mail from an end-user carefully as a request for further developments. The documentation is pragmatic and basic, the contract with the company that developed the code was based on collaboration on a rough set of features which should eventually work, rather than detailed descriptions. Development on the code continued beyond the contract requirements, for example when the actual usage of the website required it. Plans are being adapated to changes continuously, rather than where a plan first gets implemented and then evaluated.
