• risk: nature of software
• risk: team dynamics
• risk: roles
• risk: resources
• risk: analysis
• risk: architecture
• risk: design
• risk: implemention
• risk: quality assurance
• risk: project management
• risk: technologies
• risk: tools

There is a risk from software tools. Tools can be immature or inadequate for the project at hand. In general, tools should not be changed while a project is underway. However, one also needs to be nimble in this regard. I've often seen where a great tool is not adopted because of analysis paralysis.

Some examples of software tools that need to be carefully selected:

• configuration management
• wireframing
• graphical design
• code construction
• issue tracking
• logging
• dev stack environments
• test data creation

The last two are commonly overlooked and will discussed in the next section.