If you ask a dozen people on a software team to describe how the team should build software, you'll get at least a dozen different answersand most of those descriptions, if followed, will produce something. But what's produced may not be very good: it may not be useful to the users, it may not be of very high quality, and the team may not be comfortable building, delivering, or maintaining it. A software process makes sure that everyone on the team agrees up front on how they will build software, while simultaneously ensuring that the software will be built in a way that works for the team and the organization. |