Navigation Section
Collaboration Index
Project PASS PMP
This folder contains all documentation for our communications and collaboration systems under the PACE framework (Primary, Alternate, Contingency, Emergency).
It explains how we meet, communicate, share files, track work, and publish deliverables.
System Overview
- Messaging Platform (Pumble): Central hub for day-to-day coordination. Keeps all communication searchable, persistent, and professionally archived.
- Formal & Informal Meeting Platform (Jitsi): Used for all live sessions and scrums. Browser-based, secure, and requires no downloads or sign-ins.
- Task & Workflow Platform (Trello): Visual board for tracking assignments, blockers, and progress through each study cycle.
- File Collaboration Platform (Google Drive): Shared workspace for drafting, editing, and storing active files before final publication.
- Archival & Publication Platform (GitHub): Long-term repository and public access site for finalized materials.
- Alternate & Contingency Tools (Slack, Google Meet, WhatsApp, Email/SMS): Backup systems for continuity if any primary platform becomes unavailable.
Team members should review this page first, then follow the wiki links to specific platform guides for detailed setup and procedures.
1. Primary Systems
- Pumble β Primary chat and coordination hub for daily messaging and file exchange.
- Jitsi β Primary meeting platform for all formal sessions and scrums.
- Trello β Task and workflow management board for deliverables and study assignments.
- Google Drive β Central file workspace for working drafts, meeting minutes, and collaboration documents.
- GitHub β Long-term archive and publication site for finalized materials.
2. Alternate and Contingency Tools
- Slack β Alternate chat option if Pumble is unavailable.
- Google Meet β Alternate meeting link used only when Jitsi cannot host.
- WhatsApp β Informal coordination channel if all structured systems fail.
- Email and SMS β Final fallback for accountability and communication verification.
3. Key References
- PACE Communications Policy β Defines approved tools and continuity structure.
- Weekly Scrum Agenda β Outlines Saturday meeting structure and attendance rules.
- Roles and Responsibilities β Defines facilitator, scribe, and member duties.
Quick Facts (Level-2 Scan)
- Weekly formal meeting: Saturday, 10 a.m. CST
- Agenda & minutes distributed by Wednesday
- Minimum quorum: 1 Facilitator + 1 Scribe + 2 Team Members
- Repository: https://jasytionline.github.io/S33-project-managment/
- PACE: Pumble β Slack β WhatsApp β Email/SMS
Further Detail
Each linked page in this folder provides a detailed βhow-toβ for setup, configuration, and best practices on that platform.