Repository navigation
03 workflows team collaboration
Effective team collaboration using the Coherence APM Framework v4.2.0 requires coordination across multiple developers using the 11 specialized personas, voice notifications for real-time feedback, and shared context through the .apm/session_notes/ directory. This workflow ensures seamless teamwork while maximizing the benefits of unified context engineering.
-
Unified Context Engineering: All team members share context through
.apm/session_notes/directory - Clear Persona Ownership: Defined responsibilities using 11 specialized personas
- Voice-Enhanced Communication: Audio notifications provide real-time progress updates
- Session-Based Coordination: Session notes maintain team coordination and handoffs
- Collective Context Preservation: Shared responsibility for maintaining unified project context
- Command-Driven Workflows: Consistent use of 67 available slash commands across team
Team Lead (Coherence Orchestrator)
├── Frontend Developer (/design-architect + /dev personas)
├── Backend Developer (/developer persona)
├── QA Engineer (/qa persona)
├── System Architect (/architect persona)
├── Product Owner (/po persona)
├── Scrum Master (/sm persona)
├── Business Analyst (/analyst persona)
└── Product Manager (/pm persona)
Sprint 1: Developer leads with /dev and /planning-stories
Sprint 2: QA leads with /qa and /qa-framework
Sprint 3: Architect leads with /architect and system design
Sprint 4: Product Owner leads with /po and /planning-groom
Complex Feature: Team uses parallel commands for coordination
- Multiple Developers using /dev and /developer personas
- QA coordination using /qa-acceptance-criteria
- Architecture guidance using /architect persona
- Product oversight using /po and /planning-validation
- Voice notifications keep team synchronized
Team Lead: /coherence → Unified context coordination
├── Developer 1: /dev → Frontend implementation
├── Developer 2: /developer → Backend implementation
├── QA Engineer: /qa-framework → Testing coordination
├── Product Owner: /planning-stories → Story management
└── Scrum Master: /planning-next-story → Sprint progression
Voice Coordination:
- Audio notifications keep team synchronized
-
/switchand/handoffcommands preserve context - Session notes in
.apm/session_notes/shared across team
QA Lead: /qa-framework → Testing strategy
├── Developer 1: /dev → Implementation with quality focus
├── Developer 2: /developer → Code review and validation
├── QA Engineer: /qa-acceptance-criteria → Criteria validation
└── Architect: /architect → Quality architecture review
Product Manager: /pm → Product strategy
├── Business Analyst: /analyst → Requirements gathering
├── Product Owner: /planning-stories → Story creation
├── Architect: /architect → System design
├── Design Architect: /design-architect → UI/UX design
└── Scrum Master: /planning-checklist → Planning validation
Coordination Mechanisms:
- Daily Standups: Progress updates using session notes
- Integration Points: Regular integration testing and validation
- Shared Artifacts: Common backlog.md and session notes
- Communication Protocols: Clear escalation and decision-making processes
Feature Lead: /po → Requirements and priorities
├── Frontend Dev: /design-architect → UI/UX implementation
├── Backend Dev: /dev → API and business logic
├── QA Engineer: /qa-framework → Testing strategy
└── DevOps: /parallel-automation-plan → CI/CD setup
Success Factors:
- Feature Ownership: Clear accountability for feature completion
- Cross-Functional Skills: Team members understand each other's work
- Quality Gates: Shared quality standards and checkpoints
- Customer Focus: Direct connection between team and customer value
Problem Identified: Critical production issue
├── Developer: /qa-anomaly → Issue investigation
├── Architect: /parallel-course-correction → System analysis
├── QA: /qa-framework → Impact assessment
└── PM: /stakeholder-review → Communication management
Rapid Response Features:
- Parallel Investigation: Multiple perspectives on the same problem
- Coordinated Response: All team members working toward same solution
- Clear Communication: Stakeholders kept informed throughout resolution
- Learning Capture: Post-incident analysis and process improvement
Purpose: Single source of truth for all project progress Updates: All team members must update after any work Structure: Standardized format for consistent interpretation Access: Read/write access for all team members
Multi-User Update Protocol:
**[YYYY-MM-DD HH:MM] - [Name/Persona]**: [Update description]
Action: [What was done]
Stories Affected: [Which stories were updated]
Next Steps: [What needs to happen next]
Blockers: [Any issues encountered]Purpose: Document individual work progress and decisions Sharing: Shared directory, individual files per session Integration: Reference relevant team member sessions in your own notes Continuity: Handoff information between team members
Purpose: Architecture decisions, API specs, deployment procedures Maintenance: Collaborative maintenance by all technical team members Standards: Consistent documentation standards across team Reviews: Regular review and update cycles
Morning Standup (10 minutes):
- Yesterday: What did you accomplish?
- Today: What will you work on?
- Blockers: What's preventing your progress?
- Coordination: Any dependencies on other team members?
Progress Updates (As needed):
- Update backlog.md when story status changes
- Update session notes with significant progress
- Immediate communication for blockers or issues
- Proactive communication about dependencies
End of Day Summary (5 minutes):
- Update session notes with daily accomplishments
- Plan next day priorities
- Identify any overnight blockers for next day standup
Sprint Planning (1-2 hours):
- Review sprint goal and capacity
- Assign stories to team members
- Identify dependencies and coordination needs
- Commit to sprint backlog
Mid-Sprint Check (30 minutes):
- Review sprint progress and burndown
- Address any blockers or issues
- Adjust assignments if needed
- Plan for sprint completion
Sprint Review & Retrospective (1 hour):
- Demo completed features to stakeholders
- Discuss what went well and what could improve
- Update team processes and agreements
- Plan improvements for next sprint
When: Minor disagreements about implementation approach Process: Direct discussion between involved team members Timeline: Resolution within 1 day Escalation: If no resolution, escalate to Level 2
When: Technical decisions affecting multiple team members Process: Team discussion during daily standup or dedicated session Decision Making: Consensus preferred, architect decides if needed Documentation: Document decision rationale in session notes
When: Business priority conflicts or resource allocation disputes Process: Involve Product Owner or Project Manager Timeline: Resolution within 2-3 days maximum Impact: May require scope or timeline adjustments
All team members start work simultaneously on related stories
├── Developer A: Story 1 (Frontend)
├── Developer B: Story 2 (Backend)
├── Developer C: Story 3 (Database)
└── QA Engineer: Testing framework for all stories
Benefits:
- Maximum Velocity: All team members contributing simultaneously
- Integrated Progress: Features develop in coordinated fashion
- Shared Understanding: All team members understand full feature
Coordination Requirements:
- API Contracts: Agreed interfaces between frontend and backend
- Database Schema: Shared understanding of data model
- Testing Strategy: Consistent testing approach across all components
Primary development sequence with parallel support work
├── Lead Developer: Core feature implementation
├── Supporting Developer: Supporting features and infrastructure
├── QA Engineer: Test framework and validation (parallel)
└── Architect: Code review and guidance (parallel)
Benefits:
- Clear Leadership: One person drives core implementation
- Parallel Support: Other team members provide essential parallel work
- Quality Assurance: Continuous quality review and testing
Team members work on areas of expertise with cross-collaboration
├── Frontend Expert: UI/UX implementation with UX review
├── Backend Expert: Business logic with architecture review
├── QA Expert: Testing strategy with requirements validation
└── DevOps Expert: Deployment automation with security review
Benefits:
- Leverage Expertise: Each person works in area of strength
- Cross-Training: Knowledge sharing across expertise areas
- Quality Focus: Expert review of all work areas
- Story Completion Rate: Stories completed per sprint per team member
- Team Velocity: Total story points completed per sprint
- Velocity Consistency: Variation in velocity between sprints
- Parallel Efficiency: Speedup achieved through parallel development
- Communication Frequency: Updates per day per team member
- Conflict Resolution Time: Average time to resolve disagreements
- Context Sharing: How well team members understand each other's work
- Knowledge Transfer: Success rate of handoffs between team members
- Defect Rate: Defects per story point (team responsibility)
- Code Review Effectiveness: Issues caught in review vs. production
- Test Coverage: Percentage of code covered by tests
- Documentation Quality: Currency and completeness of shared documentation
- Cross-Training: Team members learn each other's expertise areas
- Pair Programming: Knowledge sharing through collaborative coding
- Code Reviews: Learning through review of each other's work
- Knowledge Sharing: Regular sessions on technical topics
- Retrospectives: Regular process improvement discussions
- Tool Optimization: Better tools and automation for team collaboration
- Workflow Refinement: Continuous improvement of development workflow
- Communication Enhancement: Better communication tools and practices
- Team Building: Activities to improve team cohesion
- Conflict Resolution Training: Skills for handling disagreements constructively
- Leadership Development: Rotating leadership opportunities
- Recognition: Celebrating team and individual achievements
Problem: Team members work in isolation without sharing context Impact: Inconsistent solutions, integration conflicts, duplicated work Solution: Mandatory session note sharing, regular integration points
Problem: Too many meetings and status updates slow down development Impact: Reduced development time, meeting fatigue, delayed decisions Solution: Structured communication protocols, focused meetings, async updates
Problem: Team members follow different coding, testing, or documentation standards Impact: Inconsistent codebase, difficult maintenance, quality issues Solution: Agreed team standards, code reviews, automated enforcement
Problem: Unclear who is responsible for specific work or decisions Impact: Work falls through cracks, conflicts over direction, accountability gaps Solution: Clear ownership definitions, RACI matrices, regular ownership reviews
- Update Frequency: Define how often team members should provide updates
- Communication Channels: Establish which channels for which types of communication
- Decision Documentation: Always document important decisions and rationale
- Escalation Procedures: Clear process for escalating issues or conflicts
- Code Ownership: Collective ownership of all code, not individual ownership
- Quality Standards: Shared responsibility for meeting quality standards
- Knowledge Sharing: Everyone responsible for sharing knowledge with team
- Process Improvement: All team members contribute to process improvement
- Regular Retrospectives: Learn from both successes and failures
- Skill Development: Invest in developing both individual and team skills
- External Learning: Bring external knowledge and practices to the team
- Experimentation: Try new approaches and tools to improve collaboration
- Right Tools: Use tools that enhance rather than hinder collaboration
- Process Automation: Automate routine tasks to focus on creative work
- Information Radiators: Make important information visible to all team members
- Feedback Loops: Quick feedback on work quality and process effectiveness
-
/coherence- Team lead coordination and orchestration -
/stakeholder-review- Include stakeholders in team decisions -
/parallel-*- Multiple team members working on related tasks
-
/session-note-setup- Establish team session note standards -
/groom- Team-based backlog grooming and planning -
/prioritization- Collaborative priority setting
-
/qa-framework- Team-based quality validation -
/qa-framework- Establish team quality standards -
/parallel-course-correction- Team-based problem resolution
### Team Performance Dashboard - Week of [Date]
#### Velocity Metrics
- **Team Velocity**: 34 story points (target: 32)
- **Completion Rate**: 94% (target: 85%+)
- **Parallel Efficiency**: 3.2x speedup (target: 2.5x+)
#### Collaboration Quality
- **Communication Score**: 8.5/10 (daily updates, minimal conflicts)
- **Knowledge Sharing**: 95% (all team members understand current work)
- **Conflict Resolution**: 1.2 days average (target: <2 days)
#### Quality Metrics
- **Defect Rate**: 0.6 per story point (target: <1.0)
- **Code Review Coverage**: 100% (all code reviewed)
- **Test Coverage**: 92% (target: >90%)
- **Documentation Currency**: 98% (documentation up-to-date)
#### Process Health
- **Standup Attendance**: 100%
- **Retrospective Participation**: 100%
- **Process Improvement Items**: 3 implemented this week- Shared Session Notes: Team members can read each other's session notes
- Context Handoffs: Structured handoffs between team members
- Work Continuity: Team members can continue each other's work
- Multi-User Updates: Multiple team members updating backlog.md
- Shared Progress Tracking: Team-wide visibility into project progress
- Collaborative Planning: Team-based sprint and release planning
- Team Parallel Patterns: Multiple team members executing parallel development
- Coordinated Streams: Coordination between parallel development streams
- Shared Resources: Team sharing of development resources and expertise
- Session Management - Individual work documentation within team context
- Backlog Workflow - Shared project tracking and progress management
- Parallel Development - Team-based parallel development patterns
- Handoff Patterns - Structured transitions between team members
Build high-performing development teams through structured collaboration, clear communication, and shared responsibility for project success.