---
title: 03. Project Planning
---

:::caution[Programme Sunset]
The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.

I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.

Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
:::

**ESTABLISHING PROJECT PLANNING PROCEDURES AND REQUIREMENTS FOR MENTORSHIP PROGRAMME PARTICIPANTS**

## 1. INTRODUCTION AND LEGAL FRAMEWORK

### 1.1. Policy Overview

This Project Planning Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for flagship project planning within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.

### 1.2. Scope and Applicability

This Documentation applies to all participants in our Mentorship Programme following completion of goal-setting procedures. All participants should complete the project planning process set forth in this Documentation to proceed with flagship project development.

**IMPORTANT: This is a self-guided process. You will create your own project plan using provided examples and templates. No approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**

## 2. PROJECT PLANNING INITIATION

### 2.1. Timing and Prerequisites

Project planning procedures must be initiated following completion of goal-setting procedures and roadmap confirmation as outlined in our [Goal-Setting Documentation](/mentorship/02-goal-setting).

### 2.2. Project Planning Forum Post Creation

**Required Action:** Create a post in the #🗺️│quest-board forum channel on our Discord community.

**Post Naming Convention:**
```markdown
<full name> - Project Plan
```

**Naming Requirements:**
- Use your full legal name or preferred full name
- Follow the exact format: "[Full Name] - Project Plan"
- Ensure consistency with goal-setting documentation

```markdown
<full name> - Project Plan
```

### 2.3. Project Idea Documentation

**Required Information:**
- Provide as much detail as possible regarding your flagship project idea
- Include project objectives, features, and technical requirements
- Describe how the project aligns with your career goals and learning objectives
- Explain how the project incorporates your personal interests

**Project Idea Assistance:**
- If you do not yet have a project idea, create your post with a statement such as: "I need help brainstorming a project idea"
- Review project idea examples in the resource library for inspiration
- Ask for help in the #⚗️│alchemy-lab channel if you'd like community input
- Programme leadership and community members can provide feedback if requested
- You can also proceed independently by researching project ideas online or adapting examples

## 3. PROJECT PLAN DEVELOPMENT

### 3.1. Self-Guided Development Process

Once your project planning post is created, you will develop your project plan independently. Use the following guidance:

- Review project plan examples in the resource library
- Flesh out and refine your project concept
- Develop comprehensive project specifications
- Establish technical requirements and architecture considerations
- Create a detailed project plan ready for development work

**Optional Support:**
- If you need help brainstorming or refining your project idea, ask in the #⚗️│alchemy-lab channel
- Community members and programme leadership can provide feedback if requested
- You can proceed independently once you have a project concept you're happy with

### 3.2. Project Plan Example

The following example illustrates the level of detail expected in a comprehensive project plan:

```markdown
A life task tracker app thats open source and self-hosted as well as a live version hosted on my website with user auth and such. Could have kanban boards and different views and such, and have tasks that depend on other tasks just like on a github projects board.

Could also link rewards to tasks / projects. e.g. Car Maintenance project with sub tasks of cleaning car, changing oil, buying car charger for cig lighter port etc, and then could link to an item that you will buy for yourself as a reward for when the entire project is complete, and itll have a link to that item when you mark the project as complete

At the end I could sneak some gamification elements in as an opt-in thing where you can level up and such by completing tasks / projects/ completing life goals).
```

Additional project plan examples are available in the resource library.

### 3.3. Project Plan Completion

**No Approval Required:**
- You do not need approval or sign-off to proceed
- Once you have created your project plan, you are ready to proceed to user story development
- Your project plan is a living document that you can update as needed

**Next Steps:**
- Upon creating your project plan, you are ready to proceed to user story development
- User story development procedures are outlined in our [User Stories Documentation](/mentorship/04-user-stories)
- Optional: You may share your project plan in Discord if you'd like feedback, but this is not required

## 4. LIMITATION OF LIABILITY AND DISCLAIMERS

### 4.1. Reference to Comprehensive Liability Framework

**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**

### 4.2. Project Planning Disclaimer

This Documentation establishes project planning procedures and requirements. However:

- Programme leadership reserves the right to modify project planning procedures at any time
- Project plans are created by participants and serve as guidance, not guarantees
- Programme leadership is not responsible for participants' ability to complete projects as planned
- Individual results may vary based on participant effort, circumstances, and other factors
- Reviews and approvals are optional and available upon request

### 4.3. Intellectual Property Considerations

All project work completed as part of the Mentorship Programme is subject to our Mentorship Programme Terms and Conditions regarding intellectual property rights. Participants should familiarise themselves with these terms before beginning project development.

## 5. CONCLUSION

This Project Planning Documentation establishes the procedures and requirements for flagship project planning within our Mentorship Programme. All participants must complete these procedures to progress to project development stages.

Questions about project planning procedures should be directed to programme leadership through designated communication channels. For comprehensive programme terms and conditions, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).

---

*For questions about project planning procedures or programme participation, please contact programme leadership through the designated channels outlined in our Community Code of Conduct.*

:::tip[Helpful Links]
- [Join Discord](https://chat.nhcarrigan.com/) - Select the mentorship role to get started
- [Donate](https://donate.nhcarrigan.com/)
:::