# Project Initiation - Resources - [Project Initiation Glossary | Google](https://docs.google.com/document/d/1NnRFDj6zKTWb4ZnCWlMt2lXh7wZoF9uj9RnJKP56s3A/template/preview) - [7 Lessons to Learn from a Failed Project | Project-Management.com](https://project-management.com/7-lessons-to-learn-from-a-failed-project/) > [!danger] Initiation Missteps > > - Unclear expectations > - Unrealistic expectations > - Miscommunication > - Lack of resources > - Scope creep ## Components - Perform _[[cost-benefit-analysis|Cost-Benefit Analysis]]_. > [!summary] Key Components of Project Initiation > > - Goals > - Scope > - Deliverables > - Success criteria > - Stakeholders > - Resources - _Stakeholder_ = people who have interest in, and are affected by, the completion and success of a project. - Use _Project Charter_ to document the details about a project. Charter is reviews by stakeholders, once approved, move to [[project-execution|execution]] phase. > - Active listening to the stakeholders. > - Slow down and look at the landscape before you. ## Goal - Project Goal = the desired outcome of a project, the clearer and more specific the better - Setting [[smart|SMART]] goals. - [[okr|OKRs]] ## Scope - Scope = Project boundaries (budge, timeline, etc.), what is included and excluded from the project. - In-scope vs out-of-scope tasks. - Scope Creep - Changes, growth, and uncontrolled factors that affect a project's scope at any point after the project begins - External vs. internal creeps - Solutions - Define your project’s requirements. - Set a clear project schedule. - Determine what is out of scope. - Provide alternatives. - Set up a change control process. - Learn how to say no. - Collect costs for out-of-scope work. > [!warning] Monitor your project scope and protect it at all cost! - Triple Constraint Model = Time, Budge, and Scope, changing one impacts the other two. [Triple Constraints of Project Management Explained & Simplified | The Digital Project Manager](https://thedigitalprojectmanager.com/projects/scope-management/triple-constraint/) ## Success Criteria - Project Launch (delivery) vs Project Landing (actually put the deliverable to test) - Determining Project Success - Identify the measurable aspects - Get clarity from stakeholders on the project requirements and expectations. - Business metrics (revenue) and customer metrics (_Adoption_ and _Engagement_) - Alongside the metrics, also document: - How is it measured? - How often is it measured? - Who measures it? - Use [[okr|OKRs]] as success criteria. [Success Criteria Template | Google](https://docs.google.com/document/d/1E3OwXHMb25DpWHeJXzff9wqjuJSO6KH9aijNUAIUNpQ/template/preview?resourcekey=0-vgOO8PhLm_19ztOHb4eLJw) ## Team - Considerations - Required roles - Team size - Necessary skills - Availability - Roles - Sponsors (director) - Team Members - Customers - Users - [[project-manager|Project Manager]] - Stakeholders (primary and secondary, all of the above) - Stages - **Forming:** members feel tentative and unsure about their project roles - **Storming:** members assert their positions and jockey for power - **Norming:** working practices are established - **Performing:** team works positively and productively to achieve project goals ## [[stakeholder|Stakeholders]] ## [[project-charter|Project Charter]] ## Tools See [[project-management-tools]].