QE3-3 How Can Agile Development and the Scrum Process Overcome the Problems of the SDLC?

Question 1

What is the main issue with the SDLC (Systems Development Life Cycle) process?

Answer 1

The SDLC process is slow, assumes clear and unchanging requirements, and follows a linear sequence, which doesn’t adapt well to changing project needs.

Question 2

Why is the SDLC often referred to as the “waterfall method”?

Answer 2

It assumes progress flows in one direction—requirements → design → implementation—without going back to previous stages.

Question 3

Why does the SDLC approach work well for building physical things but not for information systems?

Answer 3

Physical projects like runways have fixed, measurable requirements, whereas information systems are abstract and change as users and business needs evolve.

Question 4

What makes information systems fundamentally different from physical systems in the context of SDLC?

Answer 4

Information systems are social, abstract, and malleable, making it harder to define and stick to clear requirements compared to physical systems.

Question 5

What are two risks of using the SDLC for information systems development?

Answer 5

1. Requirements often change during the project.
2. Users cannot fully understand or provide feedback on the system until it is completed, risking wasted time and money.

Question 6

In short, what flawed assumption does the SDLC process make?

Answer 6

It assumes that requirements are clear and fixed, which is rarely true in real-world projects.

Question 7

What are some alternatives to the SDLC process mentioned in the material?

Answer 7

Alternatives include rapid application development, the unified process, joint application design, extreme programming, Rational Unified Process, and Scrum.

Question 8

What is Agile Development?

Answer 8

Agile Development is a development process that conforms to specific principles designed to address the problems of the SDLC.

Question 9

What are the key principles of Agile Development?

Answer 9

Expect and welcome changes in requirements.

Frequently deliver a working version of the product.

Work closely with customers for the duration.

Design as you go (just-in-time design).

Test as you go.

The team knows best how to adapt and improve.

Applicable to business processes, information systems, and applications development.

Question 10

Why does Agile Development welcome changes in requirements?

Answer 10

Because systems are meant to help organizations adapt to changing strategies, making them more effective and satisfying for users and the development team.

Question 11

How often does Agile Development aim to deliver working product versions?

Answer 11

Agile Development aims to deliver working versions every 1 to 8 weeks, minimizing risk and ensuring incremental value.

Question 12

What is “just-in-time design” in Agile Development?

Answer 12

It is a principle where only the portions of the design necessary to complete the current work are created, instead of designing the entire system upfront.

Question 13

Why is testing integral to Agile Development?

Answer 13

Testing occurs continuously during development, ensuring both team members and customers assess the product regularly for feedback and improvement.

Question 14

How does Agile Development ensure teams improve continuously?

Answer 14

Teams regularly assess their strengths, weaknesses, and bottlenecks after each deliverable or milestone to improve processes.

Question 15

In what areas can Agile Development be applied?

Answer 15

Agile Development can be used for creating business processes, information systems, and other team-based projects.

Question 16

How is Agile Development structured compared to the SDLC?

Answer 16

Agile Development is structured with shorter, iterative activities, making it more dynamic and adaptable than the SDLC’s rigid, linear process.

Question 17

What is the Scrum process, and what drives it?

Answer 17

Scrum is an agile development process driven by a prioritized list of requirements created by users and business sponsors.

Question 18

How long do Scrum work periods typically last?

Answer 18

Scrum work periods can range from 1 to 8 weeks, with 2 to 4 weeks being recommended.

Question 19

What are the key activities during each Scrum work period?

Answer 19

Select requirements to deliver.

Determine tasks to perform.

Conduct daily stand-ups (15-minute meetings).

Test frequently.

Deliver a working product.

Evaluate the team’s process at the end of the period.

Question 20

What are the three principal roles in the Scrum process?

Answer 20

Product owner: Represents business interests.

Scrum master: Facilitates the process.

Team members: Typically 7 ± 2 people.

Question 21

What is a Scrum stand-up, and what questions are asked?

Answer 21

A stand-up is a daily 15-minute meeting where each team member answers:

What did I do yesterday?
What will I do today?
What’s blocking me?

Question 22

What is the purpose of frequent testing in Scrum?

Answer 22

Frequent testing ensures rapid feedback, reduces errors, and allows for continual improvement and alignment with customer requirements.

Question 23

What is paired programming in Scrum?

Answer 23

Paired programming involves two team members working on the same computer, with one writing code and the other reviewing or testing it.

Question 24

How does Scrum handle documentation?

Answer 24

Scrum focuses on minimal documentation, delivering a working version of the product instead.

Question 25

What conditions end a Scrum project?

Answer 25

The customer is satisfied with the product.

The project runs out of time.

The project runs out of money.

Question 26

What is the main advantage of Scrum over SDLC?

Answer 26

Scrum improves collaboration through iterative development cycles, frequent feedback, and early delivery of usable product increments.

Question 27

What is the challenge of Scrum’s iterative feedback process?

Answer 27

While effective, colocating users and the development team can be expensive and distracting for busy users.

Question 28

What are some challenges top management faces in systems development?

Answer 28

Failure to limit project scope.
Allowing scope creep after the project starts.

Question 29

How can end users pose challenges in systems development?

Answer 29

Lack of engagement or participation.
Resistance to adopting new systems.

Question 30

What challenges does the IS development team encounter in systems development?

Answer 30

Poor project planning.
Limited collaboration with users.

Question 31

What is “scope creep,” and why is it a risk in systems development?

Answer 31

Scope creep refers to uncontrolled changes or continuous growth in a project’s scope, often leading to increased costs and inefficiencies as executives escalate commitment without clear benefits.

Question 32

Why might end users resist a new information system?

Answer 32

Users may resist if the system changes their roles, is poorly implemented, or if organizational processes are not adapted to take full advantage of the system.

Question 33

What planning challenges do IS development teams face?

Answer 33

Teams often struggle with creating realistic schedules, coordinating activities, and avoiding missed milestones due to the uniqueness of projects and unfamiliar technologies.

Question 34

Why is collaboration critical in systems development, and how can it fail?

Answer 34

Collaboration ensures that user needs are met and issues are addressed early. Failure occurs when teams do not maintain adequate communication with end users.

Question 35

What is project management, and why is it important in systems development?

Answer 35

Project management involves overseeing development processes to ensure success. It requires collaboration, clear planning, and linking the project to business strategies.