Scribd
Upload
10 views9 pages

Chapter 2

This chapter emphasizes the critical nature of the customer-development relationship for software project success, highlighting the importance of mutual understanding and agreement on requirements. It introduces the Requirements Bill of Rights and Responsibilities for Software Customers, underscoring the need for customer involvement in the requirements development process. Key topics include identifying decision-makers, reaching consensus on requirements, and fostering a culture that respects requirements.

Uploaded by

Ngọc Chính Huỳnh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
10 views9 pages

Chapter 2

This chapter emphasizes the critical nature of the customer-development relationship for software project success, highlighting the importance of mutual understanding and agreement on requirements. It introduces the Requirements Bill of Rights and Responsibilities for Software Customers, underscoring the need for customer involvement in the requirements development process. Key topics include identifying decision-makers, reaching consensus on requirements, and fostering a culture that respects requirements.

Uploaded by

Ngọc Chính Huỳnh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

CHAPTER 2

Requirements from the


customer’s perspective
Objectives
• After finish this chapter, student should understand that
the customer-development relationship is so critical to
software project success.
• This chapter also discusses the critical issue of reaching
agreement on a set of requirements planned for a specific
release or development iteration
• Requirements Bill of Rights for Software Customers and a
corresponding Requirements Bill of Responsibilities for
Software Customers could bring to student the importance
of customer—and specifically end user—involvement in
requirements development.
Contents

1. The expectation gap


2. Who is the customer
3. The customer-development partnership
4. Requirements Bill of Rights for Software Customers
5. Requirements Bill of Responsibilities for Software
Customers
6. Creating a culture that respects requirements
7. Identifying decision makers
8. Reaching agreement on requirements
The expectation gap
Who is the customer?
The customer-development
partnership
• Customers have the right to:
1. Expect BAs to speak your language.
2. Expect BAs to learn about your business and your objectives.
3. Expect BAs to record requirements in an appropriate form.
4. Receive explanations of requirements practices and
deliverables.
5. Change your requirements.
6. Expect an environment of mutual respect.
7. Hear ideas and alternatives for your requirements and for their
solution.
8. Describe characteristics that will make the product easy to use.
9. Hear about ways to adjust requirements to accelerate
development through reuse.
[Link] a system that meets your functional needs and quality
expectations.
The customer-development
partnership
• Customers have the responsibility to:
1. Educate BAs and developers about your business.
2. Dedicate the time that it takes to provide and clarify
requirements.
3. Be specific and precise when providing input about
requirements.
4. Make timely decisions about requirements when asked.
5. Respect a developer’s assessment of the cost and feasibility of
requirements.
6. Set realistic requirement priorities in collaboration with
developers.
7. Review requirements and evaluate prototypes.
8. Establish acceptance criteria.
9. Promptly communicate changes to the requirements.
[Link] the requirements development process
Identifying decision
• decision leader makers
• decision rule
Reaching agreement on
requirements
– Customers agree that the requirements address their needs.
– Developers agree that they understand the requirements and
that they are feasible.
– Testers agree that the requirements are verifiable.
– Management agrees that the requirements will achieve their
business objectives.
The requirements baseline
What if you don’t reach agreement?
Agreeing on requirements on agile projects

You might also like