View Single Post

Default 

August 25th, 2008, 22:08
I am a software developer and system analyst - I work like this:

1) ask your customers for the most important, most essential, vital key features and functions that they want for the new software system.

2) let the customer prioritise the functions and features.

3) cut the last 20% - I love that

4) add some indispensable features (from the developers point of view)

5) make a time plan / notate the most important use-cases / make test-cases

6) begin to develop

7) make prototypes, implement the most important things first, show them to the customer, test key functions (with the customer!)

8) adjust the priorities, functions, features, test-cases (with the customer!)

iterate 6) - 8) until you are ready - if the customer is available on a daily basis, you can iterate on a daily basis.

With this agile method of software development you get nearly bug free software in a short time and fully satisfied customers. Design errors, programming errors are recognized very early and can be fixed early, that saves a lot of money.


Agile Manifesto:
* Customer satisfaction by rapid, continuous delivery of useful software
* Working software is delivered frequently (weeks rather than months)
* Working software is the principal measure of progress
* Even late changes in requirements are welcomed
* Close, daily cooperation between business people and developers
* Face-to-face conversation is the best form of communication (Co-location)
* Projects are built around motivated individuals, who should be trusted
* Continuous attention to technical excellence and good design
* Simplicity
* Self-organizing teams
* Regular adaptation to changing circumstances

For every complex problem, there is a solution that is simple, neat, and wrong. - HL Mencken
Last edited by HiddenX; August 25th, 2008 at 22:17.
HiddenX is online now

HiddenX

HiddenX's Avatar
The Elder Spy
RPGWatch Donor

#3

Join Date: Oct 2006
Location: NRW/Germany
Posts: 4,420