Project Initiation

You will develop, compile, and write important project documents for a service type project or a manufacturing product with an international component in a 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 service or a product not yet manufactured. Service projects may include IT software development, healthcare delivery, or fundraising among many others. Manufactured products can include any type of tangible, physical product, such as a consumer product for sale, or a product used within another product among many others. It is strongly suggested to use the PMBOK® Guide as a resource.
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, 2021) for further detail on the deliverables for this section.
Your milestone will consist of two parts: A milestone summary and project artifacts. It is recommended that you complete the project artifacts first, prior to writing the summary even though the summary will proceed the project artifacts. Furthermore, to optimize your time it is also recommended to create your project artifacts using any project templates that you may find on the Internet (the template format isn’t the important thing, the content you place in the template is). Your milestone summary should be an executive style summation of the important facts or issues that you would like to raise to senior leadership out of all the details that you might find in the project artifacts.
What to turn in:
Part 1 – Summation:
• The summation should be based on the content you provide in Part 2. It is advisable to work on Part 2 before Part 1. The goal of the summation is to summarize the important data points in Part 2. The goal of Part 1 is not to repeat all of the information in Part 2.
Part 2 – Appendices:
• 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.
• Project Scope Statement – including scope description, acceptance criteria, deliverable, exclusions, constraints, or assumptions.
Optional appendices you may also include:
• 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 judgement and facilitation techniques, interviews, focus groups, decision-making, prototypes, bench-marking, or other tools and techniques.
• Meetings – including information describing the profile analysis meetings.
• Resource requirements – including resource calendar, resource breakdown structure, resource constraints, and resource leveling.
• Human resource management – including organizational charts and position descriptions, responsibility chart matrix, RACI matrix, networking requirements, and pertinent organizational theory.
• Stakeholder management – including desired engagement levels for key stakeholders, and engagement assessment matrix.
Submission Requirements:
• Write 5-6 pages in length for Part 1, not including title and reference pages.
• Use headings and section headers to indicate the topic areas. Do not repeat the questions from above.
• Include introduction and conclusion.
• Write 15-16 pages in length for Part 2.
• Include title and reference pages.
• Be formatted according to APA-7 style.
• Maintain 4 scholarly sources, peer-reviewed articles published within the last 3 years, ie www.doi.org articles.

Last Completed Projects