When all you have is a hammer... Are we selecting technology for projects
based upon what we like to use, or are we making objective choices? Kevin
King attempts to resolve the age old question: Which technology is best?
Once a shop has more than one programmer, the question of how to approach
projects takes on a deeper dimension. As a solo artist, you have all the
work, but also all the flexibility. Teams need at least a minimal structure.
Agile has been touted as one of the best. Here's the counter-argument.
In today's world, users demand with new solutions to problems and changes
to existing solutions faster than traditional software engineering
methodologies can produce them. The old tried and true methods simply do not
work anymore. So what are we to do? Just write code for whoever screams the
loudest? Agile practices help provide a balance between planning,
communication with users, and doing just what needs to be done to get the
next piece of functionality accomplished.
This last installment in this series on parallel and agile development
methodologies explores some of the well-known Agile schools of thought and
offers some suggestions for how to choose — or combine — the ones that are
right for you.
In our fast-paced, modern, development environments, the old data
processing methodologies are disappearing. Large, up-front design and
development techniques can no longer meet the delivery requirements of
today's fast-paced, rapidly changing, user demands and competitive
pressures. Like it or not, MultiValue shops need to embrace the concepts of
both parallel and agile development.