When I worked for the State of Wisconsin (as a contractor), I had many great conversations with Mark and Jon about agile software development.
One day I wrote down a list of 25 thoughts on risk management and testing. Eventually I’ll weave these ideas into articles, but for now, just a <ul>
* Everyone contributes risks
* No risk exists without probability and impact
* No impact is infinite
* All impacts are measurable
* Risks drive level of design
Please banish the use of the word “Requirements” from your software development lexicon. Immediately.
For many software teams the requirements document is the king of documents.
You know the routine. The software team works with the customer (or customer proxy) to put together a “complete” list of “requirements”. Once that is done, the team writes the software implementing the requirements and voila! the project is done.
Or maybe not.
Often reading about economics, foraging for and growing food, playing silent sports, and making software. Also, ping pong!
Often playing with his 7 year old daughter. Mark is a avid runner, into martial arts, and philosophy.
Recent Comments