aigroup-workflow 1.0.0 → 1.1.0

package/skills/jarvis/engineering-team/project-management/scrum-master/references/team-dynamics-framework.md

@@ -1,561 +0,0 @@
-# Team Dynamics Framework for Scrum Teams
-
-## Table of Contents
-- [Overview](#overview)
-- [Tuckman's Model Applied to Scrum](#tuckmans-model-applied-to-scrum)
-- [Psychological Safety in Agile Teams](#psychological-safety-in-agile-teams)
-- [Team Performance Metrics](#team-performance-metrics)
-- [Facilitation Techniques by Stage](#facilitation-techniques-by-stage)
-- [Conflict Resolution Strategies](#conflict-resolution-strategies)
-- [Assessment Tools](#assessment-tools)
-- [Intervention Strategies](#intervention-strategies)
-- [Measurement & Tracking](#measurement--tracking)
-
----
-
-## Overview
-
-Understanding team dynamics is crucial for Scrum Masters to effectively guide teams through their development journey. This framework combines Tuckman's stages of group development with psychological safety principles and practical scrum-specific interventions.
-
-### Core Principles
-1. **Development is Non-Linear**: Teams may cycle between stages based on changes
-2. **Each Stage Has Value**: Every stage serves a purpose in team development
-3. **Facilitation Must Adapt**: Leadership style should match the team's developmental stage
-4. **Psychological Safety is Foundational**: Without safety, teams cannot reach high performance
-5. **Measurement Enables Improvement**: Track dynamics to guide interventions
-
-### Framework Components
-- **Tuckman's Stages**: Forming → Storming → Norming → Performing → Adjourning
-- **Psychological Safety**: Environment for risk-taking and learning
-- **Scrum Ceremonies**: Team development accelerators when facilitated well
-- **Metrics & Assessment**: Data-driven approach to team health
-
----
-
-## Tuckman's Model Applied to Scrum
-
-### Stage 1: Forming (Team Inception)
-*"Getting to know each other and understanding the work"*
-
-#### Characteristics in Scrum Context
-- **Individual Focus**: Members work independently, unsure of roles
-- **Politeness**: Conflict is avoided, everyone tries to be agreeable
-- **Dependency**: Heavy reliance on Scrum Master for guidance
-- **Ceremony Awkwardness**: Standups feel forced, retrospectives are superficial
-- **Low Velocity**: Productivity is low as team learns to work together
-
-#### Scrum Master Behaviors
-- **Directing Style**: Provide clear structure and guidance
-- **Process Champion**: Teach scrum framework and ceremonies rigorously
-- **Relationship Builder**: Facilitate team bonding and trust building
-- **Context Setter**: Explain the "why" behind practices and goals
-
-#### Key Metrics & Indicators
-| Metric | Forming Range | Assessment Method |
-|--------|---------------|-------------------|
-| Ceremony Participation | 60-80% | Attendance tracking |
-| Cross-team Collaboration | Low | Story pairing frequency |
-| Velocity Predictability | High volatility (CV >40%) | Velocity coefficient of variation |
-| Psychological Safety | 2.0-3.5/5.0 | Anonymous team survey |
-| Conflict Frequency | Very low | Retrospective themes |
-
-#### Intervention Strategies
-- **Team Charter Creation**: Define working agreements and values together
-- **Skill Inventory**: Map team capabilities and identify knowledge gaps
-- **Pairing/Mobbing**: Encourage collaborative work to build relationships
-- **Social Activities**: Team lunches, informal interactions
-- **Process Education**: Intensive scrum training and coaching
-
-#### Success Indicators
-- Consistent ceremony attendance (>85%)
-- Team members start asking questions about process
-- Initial working agreements are established
-- Some cross-functional collaboration begins
-
----
-
-### Stage 2: Storming (Productive Conflict)
-*"Working through differences and establishing team dynamics"*
-
-#### Characteristics in Scrum Context
-- **Conflict Emergence**: Disagreements about technical approaches, priorities
-- **Role Struggles**: Tension around responsibilities and decision-making authority
-- **Process Pushback**: Questioning scrum practices, suggesting changes
-- **Subgroup Formation**: Cliques or mini-alliances may form
-- **Velocity Fluctuations**: Performance varies as team works through conflicts
-
-#### Scrum Master Behaviors
-- **Coaching Style**: Guide conflict resolution without directing solutions
-- **Neutral Facilitator**: Help team work through disagreements constructively
-- **Psychological Safety Guardian**: Ensure conflicts remain productive
-- **Process Flexibility**: Adapt ceremonies to team's evolving needs
-
-#### Key Metrics & Indicators
-| Metric | Storming Range | Assessment Method |
-|--------|---------------|-------------------|
-| Conflict Frequency | Moderate-High | Retrospective action items |
-| Ceremony Engagement | Variable (70-90%) | Participation quality scoring |
-| Velocity Volatility | Moderate (CV 25-40%) | Sprint-to-sprint variation |
-| Psychological Safety | 2.5-4.0/5.0 | Team surveys + observation |
-| Process Adherence | Inconsistent | Ceremony audit scores |
-
-#### Intervention Strategies
-- **Conflict Facilitation**: Structured conflict resolution sessions
-- **Retrospective Focus**: Deep-dive into team dynamics and relationships
-- **Individual Coaching**: 1:1s to address personal concerns and conflicts
-- **Working Agreement Updates**: Revisit and refine team agreements
-- **External Facilitation**: Bring in neutral parties for significant conflicts
-
-#### Success Indicators
-- Conflicts are addressed openly rather than avoided
-- Team develops mechanisms for working through disagreements
-- Ceremony participation becomes more authentic
-- Velocity starts to stabilize
-
----
-
-### Stage 3: Norming (Agreement & Collaboration)
-*"Establishing effective ways of working together"*
-
-#### Characteristics in Scrum Context
-- **Shared Ownership**: Team takes collective responsibility for outcomes
-- **Process Refinement**: Self-organizing improvements to scrum practices
-- **Collaboration Increase**: More cross-functional pairing and knowledge sharing
-- **Ceremony Effectiveness**: Meetings become more focused and productive
-- **Velocity Stabilization**: More predictable delivery patterns emerge
-
-#### Scrum Master Behaviors
-- **Supporting Style**: Step back and let team lead, provide support when needed
-- **Impediment Remover**: Focus on external blockers and organizational issues
-- **Continuous Improvement Coach**: Help team identify and implement improvements
-- **Shield Provider**: Protect team from external disruptions
-
-#### Key Metrics & Indicators
-| Metric | Norming Range | Assessment Method |
-|--------|---------------|-------------------|
-| Self-Organization | Increasing | Decision-making autonomy tracking |
-| Ceremony Effectiveness | 80-90% | Time-to-value ratios |
-| Velocity Consistency | Good (CV 15-25%) | Rolling average stability |
-| Psychological Safety | 3.5-4.5/5.0 | Regular pulse surveys |
-| Knowledge Sharing | High | Cross-training metrics |
-
-#### Intervention Strategies
-- **Process Ownership Transfer**: Guide team to own ceremony facilitation
-- **Skill Development**: Focus on technical and collaboration skills
-- **Measurement Introduction**: Help team define their own success metrics
-- **External Relationship Building**: Facilitate connections with other teams
-- **Continuous Improvement Rhythm**: Establish regular process refinement
-
-#### Success Indicators
-- Team members facilitate some ceremonies themselves
-- Proactive identification and resolution of impediments
-- Stable, predictable velocity patterns
-- High-quality retrospectives with actionable outcomes
-
----
-
-### Stage 4: Performing (High Performance)
-*"Delivering exceptional results together"*
-
-#### Characteristics in Scrum Context
-- **Collective Excellence**: Team consistently exceeds expectations
-- **Adaptive Expertise**: Quick response to changing requirements
-- **Self-Management**: Minimal need for external direction
-- **Innovation**: Team generates creative solutions and process improvements
-- **Knowledge Multiplication**: Members actively develop others
-
-#### Scrum Master Behaviors
-- **Delegating Style**: Minimal intervention, team is largely autonomous
-- **Strategic Facilitator**: Focus on long-term team development and capability
-- **Organizational Catalyst**: Help team influence broader organizational change
-- **Mentor Developer**: Coach team members to become coaches themselves
-
-#### Key Metrics & Indicators
-| Metric | Performing Range | Assessment Method |
-|--------|---------------|-------------------|
-| Autonomy Level | High | Decision independence tracking |
-| Innovation Frequency | Regular | New idea implementation rate |
-| Velocity Excellence | High + Consistent (CV <15%) | Performance benchmarking |
-| Psychological Safety | 4.0-5.0/5.0 | Team assessment + observation |
-| External Impact | Significant | Other teams adopting practices |
-
-#### Intervention Strategies
-- **Challenge Provision**: Introduce stretch goals and complex problems
-- **Leadership Development**: Grow team members into coaches/leaders
-- **Knowledge Sharing**: Facilitate teaching other teams
-- **Strategic Alignment**: Connect team excellence to organizational goals
-- **Innovation Support**: Create space for experimentation and learning
-
-#### Success Indicators
-- Consistent delivery of high-quality work with minimal defects
-- Team serves as a model for other teams in the organization
-- Members are sought out for coaching and mentoring roles
-- Proactive contribution to organizational process improvements
-
----
-
-### Stage 5: Adjourning (Transition & Legacy)
-*"Wrapping up and transitioning knowledge"*
-
-#### Characteristics in Scrum Context
-- **Closure Activities**: Project completion or team dissolution
-- **Knowledge Transfer**: Documenting learnings and sharing expertise
-- **Relationship Maintenance**: Preserving professional networks
-- **Legacy Creation**: Ensuring practices continue beyond the team
-- **Emotional Processing**: Addressing feelings about team ending
-
-#### Scrum Master Behaviors
-- **Closure Facilitator**: Guide proper conclusion of work and relationships
-- **Legacy Curator**: Ensure knowledge and practices are preserved
-- **Transition Planner**: Help members move to new roles/teams effectively
-- **Emotional Support**: Acknowledge and process team disbanding feelings
-
-#### Key Activities
-- **Final Retrospective**: Comprehensive review of team journey and learnings
-- **Practice Documentation**: Record effective processes for future teams
-- **Knowledge Transfer Sessions**: Share expertise with successor teams
-- **Celebration**: Acknowledge achievements and relationships built
-- **Network Maintenance**: Establish ongoing professional connections
-
----
-
-## Psychological Safety in Agile Teams
-
-### Definition & Importance
-Psychological safety is the belief that one can show vulnerability, ask questions, admit mistakes, and propose ideas without risk of negative consequences to self-image, status, or career.
-
-### Google's Four Components Applied to Scrum
-1. **Ability to show vulnerability and ask for help**
-2. **Permission to discuss difficult topics and disagreements** 
-3. **Freedom to take risks and make mistakes**
-4. **Encouragement to be authentic and express oneself**
-
-### Building Psychological Safety in Scrum Teams
-
-#### Daily Standups
-- **Model Vulnerability**: Scrum Master admits own mistakes and uncertainties
-- **Normalize Help-Seeking**: "Who needs help?" vs. "Any blockers?"
-- **Celebrate Learning**: Highlight lessons learned from failures
-- **Time Protection**: Ensure everyone has space to speak
-
-#### Sprint Planning
-- **Estimation Comfort**: No judgment for "wrong" estimates
-- **Capacity Honesty**: Safe to express realistic availability
-- **Question Encouragement**: Reward curiosity and clarification requests
-- **Scope Negotiation**: Team can push back on unrealistic commitments
-
-#### Sprint Reviews
-- **Failure Normalization**: Discuss what didn't work without blame
-- **Stakeholder Preparation**: Coach stakeholders on constructive feedback
-- **Team Support**: Unified front when facing criticism
-- **Learning Focus**: Frame setbacks as learning opportunities
-
-#### Retrospectives
-- **Non-Judgmental Space**: Focus on systems, not individuals
-- **Equal Participation**: Ensure all voices are heard
-- **Actionable Outcomes**: Team commits to improvements together
-- **Confidentiality**: What's said in retro stays in retro
-
-### Measuring Psychological Safety
-
-#### Edmondson's 7-Point Scale
-1. If you make a mistake on this team, it is often held against you
-2. Members of this team are able to bring up problems and tough issues
-3. People on this team sometimes reject others for being different
-4. It is safe to take a risk on this team
-5. It is difficult to ask other members of this team for help
-6. No one on this team would deliberately act to undermine my efforts
-7. Working with members of this team, my unique skills and talents are valued and utilized
-
-#### Practical Assessment Questions
-- **Risk Taking**: "Do team members speak up when they disagree with leadership?"
-- **Mistake Handling**: "How does the team respond when someone makes an error?"
-- **Help Seeking**: "Do people admit when they don't know something?"
-- **Inclusion**: "Are all team members' ideas heard and considered?"
-- **Innovation**: "Does the team experiment with new approaches?"
-
----
-
-## Team Performance Metrics
-
-### Quantitative Indicators
-
-#### Velocity & Predictability
-- **Sprint Velocity Trends**: Improvement over time indicates team development
-- **Commitment Reliability**: Ability to deliver planned work consistently
-- **Velocity Volatility (CV)**: Lower variation indicates team maturity
-- **Forecast Accuracy**: Precision in release planning improves with development
-
-#### Quality Metrics
-- **Defect Rates**: High-performing teams have lower defect introduction
-- **Definition of Done Adherence**: Mature teams consistently meet quality criteria
-- **Technical Debt Management**: Performing teams proactively address debt
-- **Customer Satisfaction**: Ultimately reflected in user/stakeholder feedback
-
-#### Collaboration Indicators
-- **Cross-functional Work**: Story completion without handoffs
-- **Knowledge Sharing**: Pair programming, code review participation
-- **Skill Development**: Team members learning from each other
-- **Collective Ownership**: Shared responsibility for all team outputs
-
-### Qualitative Assessments
-
-#### Ceremony Quality
-- **Engagement Level**: Active participation vs. passive attendance
-- **Value Generation**: Productive outcomes from time invested
-- **Self-Facilitation**: Team taking ownership of meeting effectiveness
-- **Adaptation**: Tailoring practices to team's specific needs
-
-#### Communication Patterns
-- **Openness**: Willingness to share problems and concerns
-- **Constructive Conflict**: Disagreements lead to better solutions
-- **Active Listening**: Team members build on each other's ideas
-- **Feedback Culture**: Regular, specific, actionable feedback exchange
-
----
-
-## Facilitation Techniques by Stage
-
-### Forming Stage Facilitation
-- **Structured Introductions**: Personal/professional background sharing
-- **Explicit Process Teaching**: Step-by-step ceremony instruction
-- **Role Clarification**: Clear explanation of responsibilities and expectations
-- **Safe-to-Fail Experiments**: Low-risk opportunities to try new things
-
-### Storming Stage Facilitation
-- **Conflict Normalization**: "Conflict is healthy and expected"
-- **Ground Rules Enforcement**: Maintain respectful disagreement standards
-- **Perspective Taking**: Help team members understand different viewpoints
-- **External Processing**: Individual coaching sessions for complex issues
-
-### Norming Stage Facilitation
-- **Autonomy Building**: Gradually reduce direct intervention
-- **Process Ownership Transfer**: Team takes responsibility for improvements
-- **Skill Gap Identification**: Focus on capability development
-- **Success Pattern Recognition**: Help team understand what's working
-
-### Performing Stage Facilitation
-- **Challenge Introduction**: Stretch goals and complex problems
-- **Innovation Support**: Time and space for experimentation
-- **Teaching Opportunities**: Help team share knowledge with others
-- **Strategic Connection**: Link team excellence to organizational goals
-
----
-
-## Conflict Resolution Strategies
-
-### Healthy vs. Unhealthy Conflict
-
-#### Healthy Conflict Characteristics
-- **Task-Focused**: About work, not personalities
-- **Solution-Oriented**: Aimed at finding better ways forward
-- **Open and Direct**: Issues addressed transparently
-- **Respectful**: Maintains dignity of all parties
-- **Temporary**: Resolved and doesn't fester
-
-#### Unhealthy Conflict Characteristics
-- **Personal Attacks**: Targeting individuals rather than ideas
-- **Win-Lose Mentality**: Zero-sum thinking
-- **Underground**: Gossip and indirect communication
-- **Destructive**: Damages relationships and trust
-- **Persistent**: Continues without resolution
-
-### Conflict Resolution Process
-
-#### 1. Early Detection
-- **Retrospective Themes**: Recurring issues or tensions
-- **Ceremony Observation**: Body language, participation patterns
-- **1:1 Conversations**: Individual team member concerns
-- **Performance Indicators**: Velocity drops, quality issues
-
-#### 2. Assessment & Preparation
-- **Stakeholder Mapping**: Who's involved, who's affected
-- **Issue Clarification**: Separate facts from interpretations
-- **Desired Outcomes**: What would resolution look like?
-- **Facilitation Planning**: Process design for resolution session
-
-#### 3. Facilitated Resolution
-- **Ground Rules**: Safe space for honest dialogue
-- **Perspective Sharing**: Each party states their view
-- **Common Ground**: Identify shared interests and values
-- **Solution Generation**: Collaborative problem-solving
-- **Agreement Creation**: Clear commitments and follow-up
-
-#### 4. Follow-up & Learning
-- **Implementation Support**: Help parties honor agreements
-- **Relationship Repair**: Ongoing relationship building
-- **Process Improvement**: Learn from conflict for future prevention
-- **Team Strengthening**: Use resolution as team development opportunity
-
----
-
-## Assessment Tools
-
-### Team Development Stage Assessment
-
-#### Behavioral Indicators Checklist
-**Forming Indicators:**
-- [ ] Heavy reliance on Scrum Master for decisions
-- [ ] Polite, superficial interactions
-- [ ] Individual work preferences
-- [ ] Process confusion or resistance
-- [ ] Low ceremony engagement
-
-**Storming Indicators:**
-- [ ] Open disagreements about approach
-- [ ] Questioning of established processes  
-- [ ] Subgroup formation
-- [ ] Inconsistent performance
-- [ ] Emotional reactions to feedback
-
-**Norming Indicators:**
-- [ ] Collaborative problem-solving
-- [ ] Process adaptation and improvement
-- [ ] Shared responsibility for outcomes
-- [ ] Constructive feedback exchange
-- [ ] Stable performance patterns
-
-**Performing Indicators:**
-- [ ] Self-organization without external direction
-- [ ] Proactive problem anticipation
-- [ ] Innovation and experimentation
-- [ ] Mentoring of other teams
-- [ ] Exceptional results consistently
-
-### Psychological Safety Assessment Survey
-
-#### Team Member Self-Assessment (5-point Likert Scale)
-1. **Mistake Tolerance**: "When I make a mistake, my team supports me in learning from it"
-2. **Voice Safety**: "I feel comfortable challenging decisions or raising concerns"
-3. **Inclusion**: "My unique perspective is valued by the team"
-4. **Risk Taking**: "I can take calculated risks without fear of negative consequences"
-5. **Help Seeking**: "I can admit when I don't know something without judgment"
-6. **Authenticity**: "I can be myself without pretending or hiding parts of my personality"
-7. **Innovation**: "We try new approaches even if they might not work"
-
-#### Behavioral Observation Checklist
-- **Speaking Up**: Team members voice disagreements respectfully
-- **Mistake Response**: Errors are discussed openly for learning
-- **Help Seeking**: People admit knowledge gaps and ask for assistance
-- **Experimentation**: Team tries new approaches without excessive fear
-- **Inclusion**: All members participate actively in discussions
-- **Feedback**: Constructive criticism is given and received well
-
----
-
-## Intervention Strategies
-
-### Stage-Specific Interventions
-
-#### Forming → Storming Transition
-- **Trust Building Activities**: Structured sharing and team bonding
-- **Psychological Safety Foundation**: Establish ground rules for safe conflict
-- **Process Education**: Deep training on collaboration and communication
-- **Individual Coaching**: Prepare team members for productive disagreement
-
-#### Storming → Norming Transition
-- **Conflict Resolution Skills**: Training in constructive disagreement
-- **Working Agreement Updates**: Refine team collaboration standards
-- **Success Celebration**: Acknowledge progress through difficult conversations
-- **Process Ownership**: Begin transferring facilitation responsibilities
-
-#### Norming → Performing Transition
-- **Challenge Introduction**: Stretch goals to push team capabilities
-- **Leadership Development**: Grow coaching and mentoring skills
-- **Innovation Support**: Create time and space for experimentation
-- **External Engagement**: Opportunities to influence other teams
-
-### Crisis Interventions
-
-#### Performance Regression
-**Symptoms**: Sudden drops in velocity, quality, or team satisfaction
-**Interventions**:
-- Team health check and root cause analysis
-- Individual 1:1s to understand personal factors
-- Process audit to identify systemic issues
-- Targeted support for specific capability gaps
-
-#### Psychological Safety Violations
-**Symptoms**: Team members withdrawing, avoiding risk, or leaving
-**Interventions**:
-- Immediate protective actions for affected individuals
-- Team-wide discussion of psychological safety principles
-- Leadership coaching for those who violated safety
-- System changes to prevent future violations
-
-#### External Pressure Impact
-**Symptoms**: Team stress, process shortcuts, decreased collaboration
-**Interventions**:
-- Stakeholder education about sustainable pace
-- Scope negotiation and priority clarification
-- Team capacity protection and workload management
-- Stress management and resilience building
-
----
-
-## Measurement & Tracking
-
-### Dashboard Metrics by Stage
-
-#### Forming Stage Metrics
-- Ceremony attendance rates
-- Individual vs. collaborative work ratios
-- Process adherence scores
-- Initial psychological safety baseline
-
-#### Storming Stage Metrics
-- Conflict frequency and resolution time
-- Ceremony engagement quality
-- Velocity volatility measures
-- Team satisfaction surveys
-
-#### Norming Stage Metrics
-- Self-organization indicators
-- Process improvement frequency
-- Knowledge sharing metrics
-- Stakeholder satisfaction
-
-#### Performing Stage Metrics
-- Innovation and experimentation rates
-- External influence and mentoring
-- Exceptional result achievement
-- Leadership development outcomes
-
-### Tracking Tools & Methods
-
-#### Regular Assessment Schedule
-- **Weekly**: Ceremony quality observation
-- **Sprint**: Velocity and quality metrics
-- **Monthly**: Psychological safety pulse survey
-- **Quarterly**: Comprehensive team development assessment
-
-#### Data Collection Methods
-- **Quantitative**: Sprint metrics, attendance, survey scores
-- **Qualitative**: Observation notes, retrospective themes, interview insights
-- **Behavioral**: Video/audio analysis of team interactions (with consent)
-- **External**: Stakeholder feedback, other team perceptions
-
-#### Progress Visualization
-- **Team Development Radar**: Multi-dimensional progress tracking
-- **Psychological Safety Trends**: Safety metrics over time
-- **Stage Transition Timeline**: Development milestone tracking
-- **Intervention Impact Assessment**: Before/after comparison
-
----
-
-## Conclusion
-
-Effective team dynamics facilitation requires understanding that team development is a journey, not a destination. Scrum Masters must:
-
-1. **Assess Accurately**: Understand current team development stage
-2. **Facilitate Appropriately**: Match leadership style to team needs
-3. **Build Safety First**: Psychological safety enables all other development
-4. **Measure Progress**: Track both quantitative and qualitative indicators
-5. **Intervene Thoughtfully**: Apply stage-appropriate interventions
-6. **Celebrate Growth**: Acknowledge progress and learning throughout the journey
-
-The goal is not just high-performing teams, but sustainable high performance built on strong relationships, psychological safety, and continuous learning. This framework provides the structure and tools to guide teams through their development journey effectively.
-
----
-
-*This framework combines research-based models with practical scrum implementation experience. Adapt the tools and techniques to fit your specific organizational context and team needs.*