Requirements Elicitation

Question 1

What is a project charter?

Answer 1

• Document that recognises the existence of a project
• Provides PM the authority to assign resources
• Specifies what various people can and cannot do
• Define goal, scope, and objectives
• Details level of quality expected
• Validates business justification
• Highlights risks

Question 2

Most things in the project charter are specified at a ____ _____ without full details. Details will be developed as the project progresses.

Answer 2

high level

Question 3

What are the first things addressed during requirements elicitation?

Answer 3

Goal, scope, objectives, and business justification

Question 4

Objectives are made for a specific ______

Answer 4

target

Question 5

What is the scope of a project?

Answer 5

Lists things that are and are not part of the project

Question 6

What 3 sections does a business justification include?

Answer 6

Business opportunity: Description of opportunity, competitors, problem being solved or improved, etc
Objective and success criteria: How business benefits from product. Quantifiable
Business Risks: Major risks associated with developing or not developing the product

Question 7

__% of causes usually cause __% of the problems

Answer 7

20, 80

Question 8

What is business analysis? What does it result in?

Answer 8

Using business justification obtained from stakeholders to gain a better understanding of the problem being solved before development begins

Results in product vision and project scope

Question 9

What is root cause analysis?

Answer 9

Finding the underlying causes of a problem that may not be immediately apparent.

Question 10

Only some root causes are worth _______

Answer 10

fixing

Question 11

What is requirements elicitation concerned with?

Answer 11

The origins of the software requirements and how we can collect them

Question 12

What are categories of elicitation challenges?

Answer 12

Scope problems
Understanding problems
Volatility problems

Question 13

A fundamental principle of good requirements elicitation is that of effective ___________ between stakeholders

Answer 13

communication

Question 14

Domain knowledge may let you suggest new workflows for your domain experts. However, they may _______ the idea

Answer 14

resist

Question 15

it’s important to make sure no only ______ stakeholders are listened to

Answer 15

vocal

Question 16

What is the distinction between customer and buyer?

Answer 16

Customer pays for the development of the software, Buyer pays for the software once it is developed

Question 17

What’s the difference between stakeholder and business requirements?

Answer 17

Stakeholder requirements are the more traditional requirements we’re used to ie user stories
Business requirements come from the project charter, business people, business analysis, business goals, and business rules & operations

Question 18

Why is requirements elicitation recursive?

Answer 18

Each iteration we go into more and more detail, then once we’re done we look back at the final picture