EAE Scope Quiz 1

The primary mission of a project is to:

• Meet the schedule baseline

• Create value

• Fully satisfy all stakeholders

• Not to overspend (exceed budget)

The Project Charter (founding, initial document that authorizes the project to begin) is:

• The list of project requirements

• Only done if PMI methodology is followed

• A high level definition of the project that includes: justification (value), objectives, high level scope, timeline and budget identification

• A "nice-to-have"; we should skip it if we don't have time to develop it

Which of the following BEST describes the Scope of the project

• The WHAT the project will do

• The HOW the project will be done

• The WHEN and for HOW MUCH the project will be done

• The WHY the project will be done

Scope is the most inamovible of the project constraints (restrictions).

• Yes, because without Scope there is no project

• No, all three main project restrictions (scope, time and cost) are equally inamovible

• Yes, beacue otherwise we will face scope creep, due to gold plating or other reasons

• Not strictly so, it may be flexible depending on the type of project

What do iterative and incremental mean?

• Iterative is developing in increasingly refined layers, and incremental is delivering usable product updates more than one time during the project timeline.

• Iterative is doing 2-week sprints in SCRUM (agile methodology) and incremental is continuously improving the product

• Iterative is re-defining the scope whenever new requirements arise, and incremental is extending the project timeline when scope is added

• Iterative is repeating requirements gathering every week or month, and incremental is adding those requirements periodically to requirements traceability matrix

Which is the best apprach for project development lifecycle?

• Agile, because it is more modern and more motivating for the teams.

• Hybrid, we should combine the old with the new, because both have good things

• The one that best fits our project and our experience. Iterations and increments are good, as long as they are applicable to our product and we can have enough knowledge in the team for this approach.

• Waterfall, it has been practiced for many more years so it is more "safe".

Which of the following is NOT true in relation to scope and requirements?

• Requirements must be documented and strurctured and reviewed periodically during scope realization

• Scope is derived from requirements

• Requirements cannot change once the detailed scope has been defined and approved

• Requirements are needs and wishes, while scope are concrete agreed-upon deliverables

You are running a project where the final users of your product are a large group of the organization's employees spread across several countries. You are interested in knowing the requirements of as many of them as possible. The budget of the project is modest. Which requirements collection technique would be the most adequate?

• An online survey

• A brainstorming session in the headquarters

• Workshops in each country

• Individual online interviews

All the following are true about requirements source documentation, EXCEPT:

• It should be retrievable when needed

• It can include emails, survey reports, meeting minutes and recordings

• It is basis for elaboration of the Requirements traceability matrix

• It is included in the scope definition document

An important stakeholder raised a valid requirement but you, the PM, know that it will not be possible to include them in the product of the project for current technical limitations. What should you do in the first place?

• Cancel the project

• Properly document it in the requirements traceability matrix.

• Tell the stakeholder that the team will be looking for a solution until it is found

• Ask for a budget extension to find an appropriate expert.