01.02.2013 Views

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

s<strong>of</strong>tware process defined<br />

Pinning down a s<strong>of</strong>tware development process<br />

You’ve read a lot <strong>of</strong> pages about s<strong>of</strong>tware development process, but we haven’t<br />

pinned down exactly what that term really means.<br />

There is no silver-bullet process<br />

There’s no single process that magically makes s<strong>of</strong>tware development succeed.<br />

A good s<strong>of</strong>tware process is one that lets your development team be successful.<br />

However, there are some common traits among processes that work:<br />

418 Chapter 12<br />

A s<strong>of</strong>tware development process<br />

is a structure imposed on the<br />

development <strong>of</strong> a s<strong>of</strong>tware product.<br />

Notice that definition doesn’t say “a s<strong>of</strong>tware development process is four-week<br />

iterations with requirements written on index cards from a user-focused point<br />

<strong>of</strong> view...” A s<strong>of</strong>tware development process is a framework that<br />

should enable you to make quality s<strong>of</strong>tware.<br />

Develop iteratively. Project after project and process after process<br />

have shown that big-bang deliveries and waterfall processes are<br />

extremely risky and prone to failure. Whatever process you settle on,<br />

make sure it involves developing in iterations.<br />

Always evaluate and assess. No process is going to be perfect<br />

from day one. Even if your process is really, really good, your project<br />

will change as you work on it. People will be promoted or quit, new<br />

developers will join the team, requirements will change. Be sure to<br />

incorporate some way <strong>of</strong> evaluating how well your process is working,<br />

and be willing to change parts <strong>of</strong> the process where it makes sense.<br />

Incorporate best practices. Don’t do something just because it’s<br />

trendy, but don’t avoid something because it’s trendy either. Most <strong>of</strong> the<br />

things that people takes for granted as good s<strong>of</strong>tware development started<br />

out as a go<strong>of</strong>y idea at some point. Be critical—but fair—about other<br />

processes’ approaches to problems, and incorporate those approaches<br />

when they might help your project. Some people call this process<br />

skepticism.<br />

Download at WoweBook.Com<br />

Wikipedia’s definition<br />

<strong>of</strong> a s<strong>of</strong>tware<br />

development process.<br />

A great<br />

s<strong>of</strong>tware<br />

process is a<br />

process that<br />

lets YOUR<br />

development<br />

team be<br />

successful.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!