Stakeholder influence is greatest at the beginning of the project

The process of determining the characteristics and features of the product of the project is called Progressive elaboration. Progressive elaboration is carried out via steps in detailed fashion.

Project verification ensuring all features and functions are included in a product or service

Project Management Plan: The project management plan provides the overall plan for executing, monitoring, and controlling, closing the project.

The Collect Requirements process occurs during project planning. Other options occur during project initiation. Option D is associated with project closing. Collect Requirements is the best option.

Bottom-up estimating: Estimating the cost of individual work items and then rolling up the costs to arrive at a project total: It is more accurate. Analogous estimating: Analogous estimating is also called top-down estimating and uses the actual cost of a previous, similar project as the basis for estimating the cost of the current project. Parametric estimating: Using project characteristics (or parameters) in a mathematical model to predict costs (e.g., price per square meter).

Activity Resource Estimate Assumptions and Breakdown StructuresIn the Estimate Activity Resources process, the key output is activity resource requirements. These requirements describe the types and quantities of resources needed for each project activity.Once you know what resources you need, you can begin to estimate the time each activity will take to complete. In this way, the activity resource requirements list generated by the Estimate Activity Resources process become inputs for the Estimate Activity Durations process.

Activity resource requirements listThe activity resource requirements list identifies, for tracking purposes, the activity's code in the work breakdown structure, as well as its name. Vital to generating the project schedule, it details the resources that you've estimated you need to complete the activity, and addresses.

Resource description – The Resource description column lists each type of resource that is required for the activity. This includes human resources, materials, and facilities.

Number required – The Number required column identifies the quantity required of each resource. This value can be specified in any measurement unit, such as hours, days, or physical number of units required.

Resource assumptions – Resource assumptions are important factors to consider when devising the project schedule. Any relevant assumptions about the resource can be included, for example resource availability, skills, or quality.

Resource availability – The Resource availability column specifies when each resource can be used. This is vital information for putting together the project schedule.

Resource dependencies – The Resource dependencies column identifies factors that may affect the availability of resources. It's important to identify dependencies when devising the project schedule because any change in an activity that has a dependency can affect the project timeline.The final row of the activity resource requirements list identifies the total resources needed for the activity. The resource totals are important in project scheduling as a base from which to calculate the duration of the activity.

Resource Assumptions - It's important to record resource assumptions, as they can help during different stages of a project. Select each project stage to find out how resource assumptions can help.

Monitoring – Recorded assumptions can affect performance monitoring. For example, if a particular task seems to be taking too long, looking at the assumptions can help you identify the problem.

Controlling – Recorded assumptions can also help you control performance. Having used the assumptions to identify a problem, you can now make performance adjustments so that the project can run more efficiently.

Closing – Recorded assumptions can provide insights during post-project assessments at the closing stage. For example, if you had made incorrect assumptions about staff capabilities, looking at the assumptions helps you understand what went wrong. This can then be recorded in the lessons learned file for the project.Failure to record assumptions can also have an impact during the Monitor and Control Project Work process.

Resource breakdown structuresAlong with the activity resource requirements list, there's one more main output of the Estimate Activity Resources process – the resource breakdown structure.The resource breakdown structure provides a hierarchical diagram of the resources required for a project. This structure is visually simple, showing resource information at a glance breaks resources into categories and resource types helps you to organize a project schedule and report on resource utilization information.

Although they look similar, a resource breakdown structure is not the same as a work breakdown structure.

A work breakdown structure, or WBS, decomposes a project into manageable units of work. Elements in a WBS include project phases, tasks, sub-tasks, and work packages. These represent all the activities in a project.

Project document updatesThe Estimate Activity Resources process concludes with project document updates – the final output of the process. Initially, various project documents are used as inputs for the process. Now that resource estimation is complete, new information may have come to light. For this reason, you may need to update documents so they reflect the latest project information.

In the process of estimating resource requirements and creating the resource breakdown structure, it's often necessary to add or delete schedule activities that appear in the activity list.The activity changes have a subsequent effect on activity attributes and resource calendars. Because project activities have changed, you need to document those changes by updating the descriptions of activities and the availability of relevant resources.

The first output of the Estimate Activity Resources process is an activity resource requirements list. It's important to record any assumptions you've made about resources in this list, for use in monitoring and controlling project work, and in post-project assessments.

A second output of the process is the resource breakdown structure. This is a hierarchical diagram that shows the resources required for the project in a visually simple way. It groups resources by category, and can be used for organizing and reporting on resources.

The final output of the process is updates to relevant project documents, such as the activity list, activity attributes, and resource calendars.

A is the correct answer. The straight-line depreciation takes the purchase value of the item, minus the salvage price of the item, divided by the number of time periods. Calculation is (5000-2000)/5 = $600.

Dedicated project team

Create the WBS is the process that follows Collect Requirements and Define Scope.

The precedence diagramming method (PDM) supports finish-to-start, finish-to-finish, start-to-start, and start-to-finish dependencies.

An electronic document repository allows all team members access to the documents, regardless of location.

project scope: The work that must be done in order to deliver a product with the specified features and functions.

Earned value analysis is used during the execution of the project to determine resource consumption versus planned

CCB should have all the mentioned characteristics.

Output of Define Scope is Project Scope statement.

There is no separate process in the Project Cost Estimation knowledge area to develop a cost management plan. It is devloped in Develop Project Management Plan process.

Projects are seeded from the recognition of a regulatory or business need.

No of communication channels: n*(n-1)/2 where n = individual. In this case 10*(10-1)/2 = 45

Adjusting Leads and Lags: Since the improper use of leads or lags can distort the project schedule, the leads or lags are adjusted during schedule network analysis to develop a viable project schedule. Tools and Techniques for Develop Schedule are : Mathematical analysis,Duration compression,Simulation,Resource-leveling ,Project management software,Adjusting Leads and Lags and Coding structure.

PMBOK describes assumptions as "factors that, for planning purposes, are considered to be true, real, or certain."

inclusion mode: Has become part of the business processes. A contract cannot contain _____________.

smoothing is a conflict resolution technique, the rest are forms of leadership power.

Rolling wave planning is providing detailed plans for tasks that are about to start in the near future using the most current information and revisiting future activities when they near their starting dates.

All the version you should keep in version control system.

Output of project initiation is formally authorizing the project. Output of project scope initiation is: Project charter PM assigned Constraints and Assumptions.

as new to project he is most likely looking for acceptance and friendship. This comes under Social need.

The scope management plan provides details about how the project scope may be changed.

A requirement document request is an input to Define Scope

Corrective action: An action that brings future project events into alignment with the project plan

Collect Requirements process starts in "Project Planning Phase" and uses the outputs of the Initiation Process.

Delivery dates and availability of resources can be found in the details of the WBS.

Acceptance is when no change to the project is made for a risk. A contingency can be set aside to offset the impact of the risk.

The project charter provides the project manager with authority.

No of communication channels: n*(n-1)/2 where n = individual. In this case 5*(5-1)/2 = 10

All are output of contract closure: Close contracts,Contract file,Lessons learned documentation and Deliverable acceptance.

The project sponsor must have the authority to select and fund the project.

Scope statement comes first in the project plan. Scope statement is the written statement of project. It contains: Project objectives, Project justification, Project deliverables

Updating the risk register first happens in Identify Risks phase. Determining risk roles and responsibilities, Identifying risk categories and developing a risk management plan are part of Plan Risk Management.

Output of Verify Scope is formal acceptance.

The project charter is the formal document for authorizes a project.

Project Quality Management includes : Customer satisfaction, Prevention over inspection, Continuous improvement, Management responsibility

The project baseline: original plans plus the approved changes.

Procurement Management is groups of processes required to purchase or acquire the products, services, or results needed from outside the project team to perform the work.

A screening system rejects sellers that does not meet minimum requirements for the project.

The product description defines the contracted work, based on the requirements of the project customer