Navigation Section
Team Charter
– Project PASS PMP
Purpose
This charter defines how the project team will work together, communicate, and resolve issues.
It outlines team values, behavioral expectations, feedback mechanisms, and conflict resolution procedures.
It supports:
- Psychological safety
- Performance alignment
- Stakeholder trust
- PMP knowledge area integration
Team Mission
To collaboratively deliver a high-quality PMP knowledge base using structured workflows, shared ownership, and clear communication — while maintaining transparency, flexibility, and continuous learning.
Team Values
| Value | Description |
|---|---|
| Accountability | Everyone owns their outcomes and deadlines |
| Transparency | Issues are raised early, honestly, and without blame |
| Respect | Disagreements are professional and constructive |
| Support | We help teammates before they ask |
| Learning | Mistakes are learning opportunities, not failures |
Communication Agreements
| Topic | Agreement |
|---|---|
| Standups / Check-ins | Weekly async updates (via Obsidian notes or GitHub issues) |
| Issue reporting | Logged in the team notes or discussed directly with the PM |
| Response time | 48-hour turnaround unless unavailable |
| File updates | Must be pushed with version and commit comments |
| Style | Clear, respectful, short-form preferred |
Conflict Resolution Path
| Step | Description |
|---|---|
| 1 | Team members attempt direct resolution |
| 2 | PM mediates in writing and offers structured solutions |
| 3 | Sponsor is brought in if unresolved within 48 hours |
| 4 | Decision is documented in a Change Request if it affects the project baseline |
Norms for Contributors
| Area | Expectation |
|---|---|
| Working Hours | Flexible; deliverables over time blocks |
| Ownership | Use the RACI Matrix to clarify responsibilities |
| Learning | Ask questions early; support others’ growth |
| Versioning | Use YAML front matter and GitHub commits for traceability |
Cross-References
Endorsement
| Name | Role | Signature | Date |
|---|---|---|---|
| Sponsor | Culture Approver | ||
| PM | Team Facilitator | ||
| Team Members | Agreement on file |
📌 This document is as binding as the schedule or scope. If our culture breaks down, the project will too. Treat it as both a promise and a protocol.