Build a Team
XΓ’y dα»±ng Δα»i nhΓ³m
XΓ’y dα»±ng team cohesion, trust vΓ high performance thΓ΄ng qua hiα»u biαΊΏt vα» Tuckman stages, diversity & inclusion, recognition vΓ team building activities.
π Tuckman's Team Development Model
πΊπΈ English
Bruce Tuckman (1965) identified 5 stages of team development. Understanding these stages helps PM anticipate team behavior and respond appropriately. Teams can move backward through stages when members change or circumstances shift significantly.
π»π³ TiαΊΏng Viα»t
Bruce Tuckman (1965) xΓ‘c Δα»nh 5 giai ΔoαΊ‘n phΓ‘t triα»n nhΓ³m. Hiα»u cΓ‘c giai ΔoαΊ‘n nΓ y giΓΊp PM dα»± ΔoΓ‘n hΓ nh vi nhΓ³m vΓ phαΊ£n hα»i phΓΉ hợp. CΓ‘c nhΓ³m cΓ³ thα» quay lαΊ‘i giai ΔoαΊ‘n trΖ°α»c khi thΓ nh viΓͺn thay Δα»i hoαΊ·c hoΓ n cαΊ£nh thay Δα»i ΔΓ‘ng kα».
| Stage | Team Behavior | PM Action | Agile Parallel |
|---|---|---|---|
| Forming Hình thà nh |
Polite, testing boundaries, uncertain roles, high dependency on leader | Clarify vision, roles, goals; establish norms; set direction | Sprint 1 kickoff; new team onboarding |
| Storming Xung Δα»t |
Conflict, resistance, power struggles, frustration; some may leave | Coach, mediate, reinforce team charter; normalize conflict as healthy | Sprint 2-3; retros surface real issues |
| Norming ChuαΊ©n hΓ³a |
Trust builds, collaboration improves, agreed ways of working | Reinforce positive behaviors, delegate, celebrate small wins | Consistent sprint velocity; DoD followed |
| Performing Hiα»u suαΊ₯t cao |
High productivity, interdependent, motivated, self-managing | Empower, protect from interference, recognize achievements | Flow state; high velocity; low defects |
| Adjourning GiαΊ£i tΓ‘n |
Project ends, sadness or relief, transition out | Celebrate, lessons learned, knowledge transfer, recognition | Project closure sprint; knowledge base handoff |
Exam Tips β Build a Team
- Storming = normal, not a failure. PM should facilitate, not suppress conflict
- Teams can REGRESS β when new member joins, or major disruption, team may return to Forming/Storming
- PM goal: reach and MAINTAIN Performing stage as long as possible
- Recognition: PM should recognize team AND individual achievements; team recognition builds cohesion
- Diversity: diverse teams perform better but take longer to norm β PM must facilitate inclusion
ποΈ Recognition & Rewards / Ghi nhαΊn vΓ Khen thΖ°α»ng
πΊπΈ English
Recognition is a powerful motivator. Key principles:
- Timely: Recognize SOON after the achievement
- Specific: Name what was done and why it mattered
- Appropriate: Match recognition to the person's preference (public vs private)
- Team vs Individual: Balance both β team celebrates collective wins; individual recognition for standout contribution
In Agile: Sprint reviews are natural recognition moments. Retrospectives acknowledge team wins.
π»π³ TiαΊΏng Viα»t
Ghi nhαΊn lΓ Δα»ng lα»±c mαΊ‘nh mαΊ½. NguyΓͺn tαΊ―c chΓnh:
- Kα»p thα»i: Ghi nhαΊn NGAY sau thΓ nh tΓch
- Cα»₯ thα»: NΓͺu rΓ΅ Δiα»u gΓ¬ ΔΓ£ Δược lΓ m vΓ tαΊ‘i sao nΓ³ quan trα»ng
- PhΓΉ hợp: Khα»p vα»i sα» thΓch của ngΖ°α»i ΔΓ³ (cΓ΄ng khai vs riΓͺng tΖ°)
- NhΓ³m vs CΓ‘ nhΓ’n: CΓ’n bαΊ±ng cαΊ£ hai
πΌ Thα»±c chiαΊΏn / Scenario
FinTech Company X β New Cross-cultural Team
TΓ¬nh huα»ng: Project Alpha team gα»m senior devs VN vΓ junior devs PH vα»«a Δược assembled. TuαΊ§n ΔαΊ§u tiΓͺn: lα»ch sα»±, Γt nΓ³i, mα»i ngΖ°α»i chα» ai ΔΓ³ lead β ΔΓ’y lΓ Forming stage.
PM actions per stage:
Forming: Tα» chα»©c team kickoff vα»i team charter workshop. Clarify roles, goals, working agreements. Introduce team to each other beyond just names β background, strengths, interests. Create Slack channel #alpha-team-intros.
Storming (Sprint 2-3): VN seniors vΓ PH juniors cΓ³ tension vα» code review expectations. PM tα» chα»©c retrospective sα»m, normalize conflict, set clear code review guidelines. Coach VN seniors vα» constructive feedback (khΓ΄ng harsh vα»i juniors).
Norming (Sprint 4+): Team establish DoD together, velocity stabilizes, pair programming becomes natural. PM celebrates: shoutout in all-hands for team completing first partner API integration.
βοΈ Practice Questions
Question 1
A newly assembled project team is experiencing frequent disagreements and some members are resistant to team processes. Which stage of team development is this, and what should the PM do?
- A. Forming β clarify roles and goals
- B. Storming β coach through conflicts and reinforce team norms
- C. Norming β celebrate team achievements
- D. Performing β give team full autonomy
β
Answer: B β Frequent disagreements and resistance indicate Storming stage. PM should coach through conflicts, help the team establish norms, and reinforce the team charter. This is normal β the PM's job is to facilitate through it, not panic.
Question 2
A previously high-performing team has recently experienced two departures and has three new members. What team development stage are they MOST likely in?
- A. Performing β they have experienced members
- B. Adjourning
- C. Back to Forming or Storming β team composition changed significantly
- D. Norming
β
Answer: C β Tuckman's model explicitly states that teams can regress when membership changes significantly. Adding three new members to a five-to-seven person team is a major disruption β new relationships must form, norms must be re-established, and trust rebuilt. The team must re-enter Forming (getting to know each other) or Storming (asserting new dynamics) even if they were previously Performing.
Question 3
The PM notices team members are starting to challenge each other's ideas in sprint planning, causing tension. This is MOST consistent with which Tuckman stage?
- A. Forming
- B. Storming
- C. Norming
- D. Performing
β
Answer: B β Storming is characterized by conflict as team members assert their individual perspectives, challenge ideas, and compete for influence. This is a healthy and necessary stage β the PM should not suppress it. The correct response is to coach through it: acknowledge the tension, reinforce psychological safety, and help the team work toward agreed norms (which leads to Norming).
π§ Team Health Check β Quarterly Review
Team Health Check β Quarterly Review
ββ PROJECT ALPHA Β· FinTech Company X Β· Q2 2026 βββββββββββββββββββββββββ
Instructions: Each team member rates 1β5 anonymously. PM calculates team average per dimension.
ββ DIMENSIONS βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Dimension | Rating (1β5) | Notes / Evidence
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Psychological safety | ___ | Can people speak up without fear of blame?
Communication quality | ___ | Is information shared clearly and timely?
Decision-making clarity | ___ | Does everyone know who decides what?
Role clarity | ___ | Are responsibilities well-defined and understood?
Conflict resolution | ___ | Are disagreements resolved constructively?
Recognition & appreciation | ___ | Do people feel their contributions are valued?
Work-life balance | ___ | Is workload sustainable? Is overtime normalized?
Team trust | ___ | Do members rely on and trust each other's work?
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
TOTAL SCORE: ___ / 40
ββ SCORING GUIDE ββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
40β50 pts β Performing # High-trust, high-output team; PM role: empower & protect
30β39 pts β Norming # Trust building; PM role: reinforce norms, celebrate wins
20β29 pts β Storming # Active conflict; PM role: coach, mediate, clarify norms
<20 pts β Forming # Low cohesion; PM role: set direction, clarify roles & goals
ββ ACTIONS ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Low-scoring dimensions (<3): [List dimensions and planned interventions]
High-scoring dimensions (5): [Recognize and preserve what's working]
Follow-up date: [Next health check in 4β6 weeks]
π€ AI Tools for PMs
How AI Augments This Process
AI helps PMs design retrospective workshops, analyze team health signals, generate team-building activities, and interpret Tuckman stage indicators from team behavior.
Sample Claude Prompts
Retrospective facilitation plan
I'm facilitating a sprint/project retrospective. Help me design it.
Team context:
Size: [number], remote/in-person: [type]
Sprint/period: [Sprint X or project phase]
Recent events: [what happened β major delivery, conflict, near-miss, success]
Team mood (my assessment): [energized / burned out / frustrated / flat]
Last retro outcome: [what was committed to β did it happen?]
Design a 60-minute retrospective using [format: Start/Stop/Continue OR 4Ls OR Sailboat OR custom]:
1. Opening activity (5 min) β psychological safety
2. Data gathering (15 min) β structured prompts
3. Insights (15 min) β dot voting or grouping
4. Action items (20 min) β SMART commitments, max 3
5. Close (5 min) β energy check
Include specific facilitation questions and watch-outs for this team's mood.
Tuckman stage assessment
I want to assess where my team is in Tuckman's model (Forming / Storming / Norming / Performing / Adjourning).
Observed behaviors:
- Conflict level: [low / medium / high β give examples]
- Decision-making: [consensus / PM-driven / contested]
- Productivity: [high / medium / low]
- Trust signals: [do people openly share problems?]
- New members recently: [yes/no]
Based on these signals:
1. Diagnose the Tuckman stage with confidence level
2. Explain 2-3 specific behaviors that led to this diagnosis
3. Give me 3 PM actions to help the team progress to the next stage
4. Warn me about regression risks (what could push them backward)
Team-building activity design
I want to design a team-building activity for my project team.
Constraints:
Team size: [number]
Remote / co-located / hybrid: [type]
Time available: [30 min / 1 hour / half day]
Budget: [none / small / reasonable]
Team's current challenge: [new team forming / trust issues / silos / post-conflict / just-for-fun]
Team culture: [formal / casual / mixed]
Generate 3 activity options (ranked by fit) with:
- Activity description and facilitation steps
- What team need it addresses
- Expected outcome
- Potential pitfall and how to avoid it
Jira / Confluence Template
Confluence β Sprint Retrospective
ββ CONFLUENCE: SPRINT RETROSPECTIVE βββββββββββββββββββββ
Sprint: [Sprint #] | Date: [YYYY-MM-DD] | Facilitator: [PM]
Attendance: [n/total] | Format: [remote / in-person]
ββ WENT WELL β² βββββββββββββββββββββββββββββββββββββββββββ
β’ [What the team said went well β verbatim or paraphrased]
β’ [...]
Votes: [top 2-3 themes with dot vote counts]
ββ COULD IMPROVE βΌ ββββββββββββββββββββββββββββββββββββββ
β’ [Pain points raised]
β’ [...]
Votes: [top 2-3 themes]
ββ ACTION ITEMS (MAX 3) ββββββββββββββββββββββββββββββββββ
1. [Specific action] β Owner: [name] β Done by: [Sprint X / date]
2. [Specific action] β Owner: [name] β Done by: [Sprint X / date]
3. [Specific action] β Owner: [name] β Done by: [Sprint X / date]
ββ PREVIOUS ACTIONS CHECK ββββββββββββββββββββββββββββββββ
From last retro: [action] β Status: [Done / Partial / Dropped β reason]
Team energy close: [1-5 scale] | Next retro: [Sprint X+1]