You are currently browsing the daily archive for June 7th, 2006.
Accumulating in software development it's a risk. Here are some examples:
- writing a lot of code without compiling is a risk
- writing a lot of code and AFTER writing unit tests is a risk
- compiling many times without running the code is a risk
- doing all this and never release to the end user is a risk
So the process of writing test, writing code, compiling, running, releasing is constituted by a set of rhythms: some are fast rock'n'roll (like the TDD: red, green, refactor), some are more a slow jazz (iteration, iteration, release, …).
So respect the basic rythms, find your tempo and keep it!
PierG
Courtesy of sylvar, Some Rights Reserved
When does a project have success??
The classical answer is: when it’s on time, on budget and with the desired quality.
In the new agile, fast and furious world, I’d add two more goals: a project is a success when it makes the customer happy and satisfied and when it makes the project team happy and satisfied.
PierG
Subscribe
