PMF05102014 Flashcards
They are the specific needs of the project
Requirements
It provides the detail what the outcome must look like
Requirements
Gathering requirements is important because if you missed truer requirements, the customer _____
Will not be satisfied with the project results
If you included requirements that are not really necessary, the project will probably ____
Take longer and cost you more than it should
Gathering requirements can be challenging. Customers and stakeholders often mix _____with truer requirements
Wish list
Another hazzard are people who are not ____often append their requirement onto your “to do list”
Stakeholders
As a project manager, you have to ______
distinguish between truer requirements and false requirements
Techniques for gathering requirements:
If your current project is like one done in the past, then try _________
Reuse
Reusing the existing requirements
Techniques for gathering requirements:
Reuse- to do this you need _____
Documentation
Techniques for gathering requirements:
Reuse- determine whether some features ____
Become obsolete or new ones have cropped up
Techniques for gathering requirements:
Another way to flesh out requirements is ____. It is usually a quick and rough model that customer could use to test out an idea.
Build prototype
Techniques for gathering requirements:
This technique is great if the customers are not sure what they want.
Build prototype
Techniques for gathering requirements:
About processes and systems
Business process model and use case
If your project involves several groups, you can hold ___with representatives of each group to discuss their requirements
Requirements meeting
You can interview ____ . Conduct observation and watch would people do on their day-to-day basis
End user
