Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 2: Requirements from the customer’s perspective (Yêu cầu từ quan…
CHAPTER 2: Requirements from the customer’s perspective (Yêu cầu từ quan điểm của khách hàng)
:question:The expectation gap
WHAT ?
a gulf between what
customers really need
and
what developers deliver
based
on what they heard at the beginning of the project
The best way to minimize the expectation gap
Arrange frequent
contact points
with suitable
customer representatives (Gia tăng contact point)
WHAT "contact point"
interviews
conversations
reviews
walkthroughs
prototype evaluations
agile development—user feedback on small increments of executable software.
Who is the
customer
?
Who is stakeholder ?
Person, group, or organization that is actively involved in a project
affected by its process or outcome (Bị ảnh hưởng bởi kết quả của project)
can influence its process or outcome(Có thể ảnh hưởng, tác động tới project)
Customers are a subset of stakeholders
Product owner
End user
Direct user
Indirect user
The customer-development partnership
Rights for Software Customers (Quyền của customer)
. Expect BAs to speak your language.
Expect BAs to learn about your business and your objectives.
Expect BAs to record requirements in an appropriate form.
Receive explanations of requirements practices and deliverables.
Change your requirements.
Expect an environment of mutual respect.
Hear ideas and alternatives for your requirements and for their solution.
Describe characteristics that will make the product easy to use.
Hear about ways to adjust requirements to accelerate development through reuse.
Receive a system that meets your functional needs and quality expectations.
Responsibilities for Software Customers (nghĩa vụ của customer)
. Educate BAs and developers about your business.
Dedicate the time that it takes to provide and clarify requirements.
Be specific and precise when providing input about requirements.
Make timely decisions about requirements when asked.
Respect a developer’s assessment of the cost and feasibility of requirements.
Set realistic requirement priorities in collaboration with developers.
Review requirements and evaluate prototypes.
Establish acceptance criteria.
Promptly communicate changes to the requirements.
Respect the requirements development process.