Project Charter- The Great Pyramid Project of Giza

1. Acceptance criteria ***Looking for assistance with this part**** The acceptance criteria can be used to determine the project selection or design options. In using these criteria, the following questions should be addressed:
2. Is this a mandated project? Answer Yes or No. Describe the rationale.
3. Describe how this project aligns with the organization's strategic or business strategies.
4. What is the current status of resource availability?
5. Project Risk - Risk management begins up front and early in the project and continues until the project is complete. Project risk assessment is a proactive process and can help the PM and his team to identify and manage potential threats to the project.

Assumprtions, Assumption Analysis, and Constraints The PMBOK Guide (2017) defines the word assumption as \"a factor in the planning process that is considered to be true, real, or certain, without proof or demonstration\" (p. 699). According to the PMBOK Guide (2017), \"Assumptions Analysis is defined as a technigue that explores the accuracy of assumptions and identifies risks {o the project from inaccuracy, inconsistency or incompleteness of assumptions\" (p. 899). For example, you may assume that your project will be fully supported and resourced throughout the project life cycle; however, if resources are constrained due to internal or external factors (e.q., your organization reassigned you to a more urgent or higher prigrity project), this could create risk. Linus, the Sphinx Project IManager, was concerned with this issue for his project. Assumptions should be documented whenever they are used. Assumptions can also be considered risks, because assumptions can impact the entire project. The term \"constraint\" is not specifically defined in the Glossary of the PMBOK? Guide (2017). The PMI Lexicon of Project Management (2012} defines a constraint as \"a limiting factor that affects the execution of a project, program, portfolio, or process\" {p. 5). Constraints are further discussed in Section 1.2.5 of the PMBOK Guide. The rationale for discussing constraints in this section of the PMBOK Guide (2017) is that constraints must be managed throughout the project lifecycle. Constraints may shift over time and repeat themselves or compete with one another based upon perspective and spatial (where) & temporal (when) relationships. This is one reason the PMBOK Guide implies that managing the project may require a balancing and competing of the following constraints: + Scope, Quality, Schedule, Budget, Resources, and Risk * These definitions are taken from the Glossary of the Project Management Institute, A Guide fo the Project Management Body of Knowledge, (PMECHK Guide) Sixth Edition, Project Management Institute, Inc, 2017 You may consider conducting an assumption/constraint analysis. You would typically conduct this analysis before updating your charter by exploring the accuracy of assumptions, constraints, risks, and impacts to the project. Focus on inaccuracy, inconsistency, or incompleteness of assumptions and constraints. Identify and add these assumptions and constraints to your Pyramid Project Charter and submit your work to the