|
We are a very pragmatic bunch of people. If a certain way of working doesn't yield result we consider it to be bad.
And contrary to what you might expect this makes us a very rare exception in business-land. Just think about how many software projects in your organization were delivered late, exceeded the budget, or even didn't 'materialize'.
When this happens regularly you should realize that your methodology is no good. It takes a bit of courage to admit such a thing but it's reality.
And once you accept the fact that not everything is up to standard you can start improving.
|
|
So how could you know that you're not yet up to standard? We present you a little checklist of things we consider an absolute necessity ...
- True Test Driven Development : you should reach a percentage over 80% of functional coverage. And preferably over 90% ... if you don't it's not good enough
- True Continuous Integration : nightly builds are not good enough, you should build anytime code gets checked in (20 builds per day are no exception for very 'active' projects)
- Functional design should be up to date AT ALL TIMES! If it isn't ... it's not good enough
|