The format for the Portfolio Project follows the project management documentation of process groups from the 6th edition of the PMBOK Guide. It is strongly suggested that students use the PMBOK Guide

The format for the Portfolio Project follows the project management documentation of process groups from the 6th edition of the PMBOK Guide. It is strongly suggested that students use the PMBOK Guide as a resource during the development of the Portfolio Project.

In this option, you will develop, compile, and write important project documents for a product type project with an international component in a for-profit or non-profit firm that you have selected. You must clearly detail the international component of your selected project. It may be that the project is executed in a country other than the United States, or that the supplier is hired from a company headquartered outside the United States. The company or organization can be one that you work for, one with which you are familiar, or one you find through research. The project must be a real project, not yet started, and for delivery of a tangible product. Product projects may include market research related to product adoption, implementing a new feature to an existing product, developing a new tangible product among many others. The project must be a new project that you will plan and must not be an existing project within the organization, nor one you have used in any previous courses in the program. Your instructor will use Turnitin to ensure all work is your own (20% match in Turnitin) for this section of this course. You must select a project that is complex enough to allow you to demonstrate an understanding of the learning objectives for this course, and that allows you to deliver on all the project management components required in this portfolio project.

Your assignment milestone is as follows:

Project Initiation – Your project plan must include an introduction of the company and the scope of the project. Your project initiation portion of the portfolio project is to include an explanation of those inputs, tools, and techniques that result in a project charter, and stakeholder register. It is strongly suggested that you consult the PMBOK Guide (Project Management Institute, 2017) for further detail on the deliverables for this section of your Capstone Project.

• Project Statement of Work (SOW) – including the business need, product, service, or result scope description, and the strategic plan to show how the project aligns with the organization’s vision, goals, and mission.
• Project Charter – which will formally authorize the project and use of resources.
• Business case – including information relative to the market demand, organizational need, customer request, technological advance, legal requirement, ecological impact, or social need.
• Stakeholder analysis – including analysis of relationships, quantitative, and qualitative information regarding interests of the parties and documented in a power/interest grid, power/influence grid, influence/impact grid, or salience model.
• Stakeholder register – including the identification information, assessment information, and stakeholder classification.
• Procurement documents – including contract information for key stakeholders and suppliers, and supplier lists.

Optionally, please include (in your appendices):

• Agreements – which define the initial intentions captured in a memorandum of understanding, service level agreement, letters of intent, or other written or verbal understanding of the project.
• Enterprise environmental factors – including governmental standards, organizational culture, organizational structure, and market considerations.
• Organizational process assets – including organizational standards, policies, templates, or processes, and historical information that informs the project team.
• Tools and Techniques – including expert judgment and facilitation techniques.
• Meetings – including information describing the profile analysis meetings.

Project Planning – It is strongly suggested that you consult the PMBOK Guide (Project Management Institute, 2017) for further detail on the deliverables for this section of your Capstone Project. To finalize your work to deliver the requirements for this portion of your portfolio project, you must include the following subsections:

• Project Management Plan – including project baselines for scope, schedule, and cost; subsidiary plans for scope management, requirements management, schedule management, cost management, quality management, process improvement management, human resource management, communications management, risk management, procurement management, stakeholder management; other items such as description of how the work will be performed, change management plan, and information on how key management reviews will be conducted.
• Traceability Matrix – including information on project requirements, rationale for inclusion, source, priority, and status.
• Project Scope Statement – including scope description, acceptance criteria, deliverable, exclusions, constraints, or assumptions.
• Create WBS WBS Dictionary – including information on decomposition, and WBS to five levels as shown in the video example in Module 4.
• Cost estimates – including basis of estimates, vendor bid analysis, cost benefit analysis, and cost of quality.
• Budget – including cost baseline, management reserve, control accounts, contingency reserve, activity contingency reserve, and project funding requirements.
• Communications management – including communication requirements analysis, communication technology, communication models and methods.
• Risk management – including analytical techniques used, risk breakdown structure; risk categories, probability, and impact matrix; risk categorization, and urgency assessment; risk register with list of risks and potential responses; use of quantitative risk modeling through tornado diagram, decision tree diagram, or cost risk simulation results; and strategies for negative and positive risks.

Optionally, please include (in your appendices):

• Tools and Techniques – including interviews, focus groups, decision-making, prototypes, benchmarking, or other tools and techniques.
• Rules for cost and performance management – including a discussion of earned value measurement (EVM) techniques.
• Activity list, attributes, and milestone list.
• Precedence diagramming method (PDM), dependency determination, task duration, and leads and lags, and critical path method (CPM).
• Project schedule network diagram with critical path, ES, LS, EF, LF, and slack.
• Resource requirements – including resource calendar, resource breakdown structure, resource constraints, and resource-leveling.
• Estimates of activity duration – including analogous estimating, parametric estimating, or three-point estimating, and reserve analysis.
• Quality – including seven basic quality tools, statistical sampling, process improvement plan, quality metrics, and quality checklists.
• Human resource management – including organizational charts and position descriptions, responsibility chart matrix, RACI matrix, networking requirements, and pertinent organizational theory.
• Procurement management – including make-or-buy analysis, market research, and source selection documents.
• Stakeholder management – including desired engagement levels for key stakeholders, and engagement assessment matrix.

Your well-written paper must meet the following requirements:

• 4-6 pages in length, not including cover, references page, and any appendices.
• Supporting documents must appear in appendices.
• The paper must be supported by at least 2 quality sources, of which 1 must be a current, scholarly resource. For this assignment, current, scholarly sources are peer-reviewed journal articles published within the most recent 3 years and accessed from the library databases or other academic sources. Textbooks will not count toward peer-reviewed requirements but may be used as quality sources if published within the most recent 3 years. The use of the PMBOK Guide as a quality source is strongly suggested. The PMBOK Guide is not a scholarly resource.