Agile

This instance exemplifies a prevalent issue in software and IT development, where programmers and IT employees are eager to lock in requirements as soon as possible so they can "get to work" without fear of invasive or disruptive input from end users. Unfortunately, the end product is usually not what the consumers wanted or believed they needed, and a long list of changes and modifications are required to make it operate properly. This case is based on a genuine tale from a hospital IT department that suffered from user disputes regularly until they adopted an Agile methodology.

Questions 1

i. Why does the traditional waterfall project planning model fail in this case? What is it in the IT department's operations that cause finished systems to be rejected regularly?

ii. How may an Agile methodology address some of these issues? What new development cycle do you advocate?

iii. Why are "user stories" and system "features" essential components of a successful IT software development process?

iv. Create an alternate development cycle for a fictional software development process at Northwest Regional Hospital using the phrases "Scrum," "Sprint," and "User stories."

Fresh replies only!