Abstract
Why do IT departments insist on having written requirements from users before they start a project when their needs are often poorly defined? There are several key problems with the waterfall development method. This led to the reanalysis of this method. In the last five years or so there has been a growing contingent with IT - the so called agile community that argue that this is the wrong way of going about things. Agile processes say that the three things that are always fixed are time, resource and quality. Only now is the IT profession starting to understand the true nature of building computer systems. And that means we all have some unlearning to do.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
