Quizzes Flashcards

1
Q

What is the purpose of a daily stand-up meeting in Agile?

A

To discuss project status and obstacles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which of the following are advantages of Agile development? (

A

Early and frequent product releases
Improved customer collaboration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

In product-based software development, which factor differentiates it from project-based software development?

A

Product updates are driven by internal business strategy rather than external client contracts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the purpose of a sprint retrospective in Scrum?

A

To review the sprint and discuss improvements for the next sprint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Which key responsibility of the Scrum Master promotes a self-organizing development team by removing impediments and facilitating continuous improvement?

A

Coaching the team on Scrum practices and resolving issues

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Non-functional requirements describe the system’s operation capabilities. T/F

A

T

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the primary purpose of stakeholder-driven elicitation techniques like interviews and workshops?

A

To collect qualitative insights directly from individuals involved in the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

During a requirements elicitation process, a team decides to conduct structured workshops where different stakeholders contribute based on their expertise. What is a key advantage of this approach?

A

It fosters negotiation and resolution of conflicting stakeholder viewpoints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Which principle of Requirements Engineering focuses on balancing business objectives, technical feasibility, and stakeholder needs to ensure that requirements add tangible value to the system?

A

Value-Orientation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a key challenge when using Observation as a Requirements Elicitation technique?

A

It may not capture tacit knowledge that users take for granted

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Documenting requirements is not necessary in agile development

A

T

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

ignore full-fledged requirements since the development is internal

A

T

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

A product backlog is primarily organized around system visions and epics.

A

F

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

User stories are the most abstract level of requirement representation.

A

F

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Use cases and scenarios are primarily used to replace user stories.

A

F

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Epics and features serve an intermediate level of abstraction, grouping user stories.

17
Q

What purpose does a system vision serve in agile requirements specification artifacts?

A

To offer an abstract overview of the system being developed.

18
Q

nature of documenting functionality in requirements

A

It should encompass data usage and structure, results, preconditions, processing, and both normal and abnormal system behaviors.

19
Q

True/False. When specifying requirements in natural language, subordinate clauses are only used for making the requirements more precise.