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 [...]
Posts Tagged ‘requirements’
25 Thoughts on Agile Development
Posted in software development methodology, tagged agile, requirements, risk management on September 2, 2009 | 6 Comments »
Nothing is required, it’s all about features
Posted in software development methodology, tagged agile, features, requirements on August 26, 2009 | 2 Comments »
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 [...]
Philip is…
Often reading, thinking about, or doing risk management, software, economics, snowboarding, running and/or ping pong.
-
Recently
Tags
-
Recent Comments
My Work
On Twitter
- I endorse @gl33p for strategy because Preston has helped hundreds of organizations with their internet strategy. @imby 3 months ago
- Lots of people seem to have drunk the kool-aid on Pivotal Tracker. I have no idea why. I'll take Roundup any day over it. 8 months ago
- Looking forward to #lessconf and #bcjax this weekend. Hammering hard getting the todo list cleaned up. 9 months ago
- "Software teams are more likely to succeed using techniques similar to movie production, rather conventional engineering projects" (IBM) 9 months ago
- RT @KevinSwiggum: Is today code like a pirate too? List<Matey__c> = Ship.getMateys(); fer (mateys : ye) { avast(ye);} 10 months ago
