• 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

Can you imagine a hockey team with forwards but no defense? Can you imagine publishing a book without an editor or publisher?

If you were having a house built, would you expect a single person to be a good electrician, plumber and carpenter?

The different parts of the SDLC require different skill sets. The most important role is that of the software architect. A good architect orchestrates the whole SDLC.

In addition to the architect, there are analysts, designers, coders, testers and project managers. There are also different subtypes for each of these roles.

A very common bad mistake is to replace the architect with a project manager. A second common bad mistake is to expect coders to analyze, architect and design, often with no time allocated. A third common bad mistake is to have no testers. It's like expecting the goalie the handle defense in a hockey game. Ideally, coders and testers work hand in hand, increasing overall productivity.