Chapter 12.7, Problem 12.6ARQ

Explanation of Solution

Explain two reasons for which SDLC is falling out of favour:

The two reasons for which Software Development Life Cycle or SDLC is falling out of favour:

• SDLC does not expect changes:
  • This nature of SDLC denies the truth that systems requirement are fuzzy and always changing.
  • In SDLC progress goes linearly from requirements to design to implementation which is a waterfall development process.
  • But business processes, Information Systems and applications are not physical but rather social; hence waterfall development does not work.
• Risk factor of SDLC:
  • It can be said that SDLC is very risky and the users for whom the process is build can’t see the product until its completion and there is a huge risk by users as it anything goes wrong by completion of the project, their money, time and resources will be wasted.

Meaning and importance of each of the principles in fig 12-20:

Fig 12.20 represents the principles of scrum:

• Scrum expects and welcomes changes in requirements:  Unlike SDLC, scrum is readily expects changes that can be made in systems requirement.
• Scrum frequently delivers working version of the product: In scrum work estimates are more and work proceeds and completes more logically.
• Scrum work closely with user unlike SDLC in which the user can see the project only after completion.
• In scrum user can design as he wants and test the product and scrum is ideal for rapidly changing and accumulating requirements.
• In scrum teams can know in details the process of the project and it is incremental in nature.
• Scrum can be used for business processes, Information Systems and applications development as compared to SDLC which can’t be used due to its waterfall model.

Essential items in fig 12-21 is implemented in scrum processes shown in fig 12-22:

Fig 12-21 represents scrum essentials and fig 12-22 represents scrum processes.

Scrum essential items are implemented in scrum processes in the following ways:

• Scrum is an agile development process having special characteristics. A prioritized list of requirements is created by user and business sponsors of the new system and the process are first driven by it. This fulfils the scrum process criteria prioritize requirement list.
• Recommended time for scrum processes is 4 to 8 weeks and the team selects the top priority items that it will commit to deliver in that period.  The team meets daily for stand up meeting and discuss their work details which give accountability to the member’s progress and give a public forum to block all factors...