wayground logo

Free Printable Worksheets

NEW

Font size

S
M
L
XL
Worksheets

Agile Software Development - Multiple Choice Questions (MCQs)

Total questions: 10

Worksheet time: 5mins

Name
Class
Date
1.

What is the main focus of Agile methodology?

a)

Writing detailed documentation before development

b)

Delivering software in small, usable parts

c)

Following a fixed plan strictly

d)

Ignoring customer feedback

2.

When was the Agile Manifesto created?

a)

1990

b)

1995

c)

2001

d)

2010

3.

Which of the following is not one of the four core values of the Agile Manifesto?

a)

Individuals and interactions over processes and tools

b)

Working software over documentation

c)

Contract negotiation over customer collaboration

d)

Responding to change over following a plan

4.

What is the primary measure of progress in Agile development?

a)

Number of meetings held

b)

Working software

c)

Amount of documentation

d)

Time spent on design

5.

Who created the Scrum methodology?

a)

Kent Beck and Jeff Sutherland

b)

Jeff De Luca and Peter Coad

c)

Ken Schwaber and Jeff Sutherland

d)

Jim Highsmith and Sam Bayer

6.

In Extreme Programming (XP), how do developers usually work?

a)

Alone to improve focus

b)

In pairs, switching roles often

c)

In large groups

d)

Only during sprints

7.

Which Agile method follows the cycle “Speculate, Collaborate, and Learn”?

a)

Scrum

b)

XP

c)

ASD (Adaptive Software Development)

d)

DSDM

8.

What is the main goal of the DSDM methodology?

a)

Deliver software quickly while meeting business needs

b)

Produce maximum documentation

c)

Avoid user involvement

d)

Build software without planning

9.

What is the main purpose of the Kanban method in Agile development?

a)

To deliver work in fixed 2–3 week sprints

b)

To visualize workflow and identify bottlenecks for continuous improvement

c)

To replace Scrum roles with new ones

d)

To focus only on long-term planning

10.

What does BDD (Behavior Driven Development) focus on?

a)

Writing long technical documents

b)

Encouraging collaboration through shared language and behavior scenarios

c)

Ignoring user feedback

d)

Planning in long cycles