Ensure Team Members / Stakeholders Are Adequately Trained
Đảm bảo Thành viên nhóm / Stakeholders được Đào tạo đầy đủ
Xác định nhu cầu đào tạo, lên kế hoạch phát triển năng lực team và đảm bảo stakeholders có đủ kiến thức để tham gia hiệu quả vào dự án.
📖 Lý thuyết / Theory
🇺🇸 English
Training is a proactive investment, not a reactive fix. PM should assess training needs at project start and continuously throughout the project as new technologies, processes, or requirements emerge.
Training sources: Formal training (courses, certification), on-the-job training, mentoring/coaching, shadowing, workshops, communities of practice.
Stakeholder training: Not just for internal team — stakeholders (especially end users or business partners) also need training on new systems, processes, or tools introduced by the project.
Reference: PMI — Project Training & Development
🇻🇳 Tiếng Việt
Đào tạo là đầu tư chủ động, không phải sửa chữa phản ứng. PM nên đánh giá nhu cầu đào tạo ngay từ đầu dự án và liên tục trong suốt dự án khi công nghệ, quy trình hoặc yêu cầu mới xuất hiện.
Nguồn đào tạo: Đào tạo chính thức (khóa học, chứng chỉ), đào tạo tại chỗ, mentoring/coaching, shadowing, workshop, cộng đồng thực hành.
Đào tạo stakeholder: Không chỉ cho team nội bộ — stakeholders cũng cần đào tạo về hệ thống, quy trình hoặc công cụ mới.
🔧 Skill Gap Analysis Template
| Skill Area | Required Level | Current Level | Gap | Training Plan | Timeline |
|---|---|---|---|---|---|
| Go microservices | Advanced | Intermediate | Medium | Internal workshop + code review sessions | 4 weeks |
| Kafka event streaming | Intermediate | Beginner | High | Online course + hands-on project | 6 weeks |
| Kubernetes deployment | Basic | None | High | DevOps team knowledge transfer | 3 weeks |
| API contract testing | Intermediate | Intermediate | None | – | – |
| PCI-DSS compliance | Awareness | None | Medium | Compliance team session (2h) | Week 1 |
💼 Thực chiến / Scenario
FinTech Company X — Onboarding New PH Team
Tình huống: 3 developers mới từ PH join Project Alpha. Họ có Go experience nhưng chưa hiểu fintech domain (loan origination, credit scoring, partner bank APIs) hay hệ thống Temporal workflow hiện tại của công ty.
Training Plan được tạo:
Week 1: Domain knowledge (loan lifecycle, partner integration flow) với Business Analyst dẫn dắt. Week 2: Codebase walkthrough với Tech Lead, review ADRs và architecture docs. Week 3-4: Pair programming với senior devs trên actual tickets, supervised PRs. Week 5+: Independent work với mentoring support.
PMP principle: Đây là T05 (Train) kết hợp với T13 (Mentor) — đào tạo không chỉ là class room learning mà là structured onboarding experience.
✏️ Practice Questions
Question 1
A PM discovers mid-project that team members lack the skills to implement a critical technical component. What should the PM do FIRST?
- A. Replace team members with people who have the required skills
- B. Assess the skill gap and develop a training plan, considering impact on schedule
- C. Outsource the component to an external vendor
- D. Reduce the scope to eliminate the component
✅ Answer: B — FIRST step is to assess the situation before taking action. A training plan addresses the gap and develops the team. Replacement (A), outsourcing (C), and scope reduction (D) are all valid options AFTER assessment shows training isn't feasible given time/cost constraints — but they're not the FIRST step.
Question 2
A new team member from a different country joins mid-project. They have strong technical skills but lack knowledge of the organization's processes and tools. What training should be prioritized?
- A. Advanced technical certifications
- B. Onboarding: org processes, tools, team norms, and project context
- C. Leadership training for future growth
- D. Training on technologies not currently used in the project
✅ Answer: B — When a new member already has technical skills, the priority gap is organizational knowledge: how things work here, what tools are used, team norms, and project context. This is the training that directly unblocks their productivity. Technical certifications (A) address a gap that doesn't exist. Leadership training (C) and unrelated technology (D) are not aligned to immediate project needs.
Question 3
What is the PM's BEST approach when a skill gap is identified that affects critical path activities?
- A. Accept the gap and reduce scope
- B. Immediately hire a replacement
- C. Assess the gap size, create a targeted training plan, and consider temporary support for critical activities while training progresses
- D. Reassign the person to non-critical tasks permanently
✅ Answer: C — A critical path gap requires a dual-track response: train the person (long-term capability) AND protect the schedule (short-term support, e.g., pair with a senior or bring in temporary expertise). Accepting scope reduction (A) is a last resort. Immediate replacement (B) is disruptive and expensive. Permanent reassignment (D) abandons the person's development without exploring solutions.
🔧 Sprint Onboarding Plan — New Team Member
Sprint Onboarding Plan — New Team Member
── PROJECT ALPHA · FinTech Company X ───────────────────────────────────
New Member: [Name] Role: [Backend Dev / Frontend Dev / QA] Start Date: [Date]
Buddy Assigned: [Senior Dev Name] Hiring Manager: Engineering Manager
── WEEK 1 · Environment & Orientation ───────────────────────────────────
□ Dev environment setup (local, staging access, VPN, SSH keys)
□ Codebase overview session with Tech Lead (repo structure, ADRs, key services)
□ Team introductions — 1:1 with each team member (15 min each)
□ Read: Team Charter, Working Agreements, Definition of Done
□ Domain knowledge session: loan origination flow, credit scoring logic (with BA)
□ Access provisioned: GitHub, Jira, Slack channels, monitoring dashboards
── WEEK 2 · First Contribution ──────────────────────────────────────────
□ Pick first small ticket (1–2 story points, well-defined scope)
□ Pair programming session with buddy on ticket implementation
□ Submit first PR — buddy reviews and gives feedback
□ Attend all sprint ceremonies: standup, grooming, review
□ Read 2 recent ADRs to understand architecture decisions
── WEEK 3 · Independent Work ────────────────────────────────────────────
□ Take independent ticket (3 story points) with buddy available async
□ Participate in code review — review a peer's PR with written comments
□ Learn and follow PR process: branch naming, commit message format, review SLA
□ Shadow PM / Tech Lead in stakeholder meeting (Bank Partner A sync)
── WEEK 4 · Full Integration ────────────────────────────────────────────
□ Participate in sprint planning — estimate stories independently
□ Contribute to retrospective: share one "went well" and one "improve" item
□ Complete onboarding checklist sign-off with EM
□ Set 30/60/90-day goals in IDP with EM
── SUCCESS CRITERIA ─────────────────────────────────────────────────────
Week 1: Environment working, codebase readable
Week 2: First PR merged
Week 3: Independent ticket delivered on time
Week 4: Full sprint participation, IDP created
🤖 AI Tools for PMs
How AI Augments This Process
AI helps PMs identify training needs, design onboarding plans, build learning paths, and generate coaching questions tailored to individual growth goals.
Sample Claude Prompts
Training needs analysis
I need to assess training needs for my team. Help me run a training needs analysis (TNA).
Team context:
Size: [number of people]
Roles: [list of roles]
Project upcoming: [what's coming — new tech, new process, go-live]
Known skill gaps (from reviews or observation): [list what you know]
Learning preferences: [online self-paced / workshops / pair programming / etc.]
Generate:
1. A skills gap matrix (role x skill, RAG status)
2. Prioritized top 5 training needs with business justification
3. Recommended learning format for each (workshop/e-learning/mentoring/on-the-job)
4. Estimated time investment per person
5. Success metric for each training item
New team member onboarding plan
I'm onboarding a new team member. Generate a 30-60-90 day plan.
Role: [title and responsibilities]
Team: [project team they're joining]
Their background: [what they know / what's new to them]
Project phase when they join: [planning / mid-execution / close]
Key stakeholders they'll interface with: [list]
Critical skills they need to develop: [list]
Create a 30-60-90 day onboarding plan with:
- Day 1-5 quick wins (who to meet, what to read, first deliverable)
- Day 30 milestone: what "productive" looks like
- Day 60 milestone: what "independent" looks like
- Day 90 milestone: what "contributing peer" looks like
- Learning resources for each phase
- Check-in cadence and success metrics
Coaching conversation questions
I'm preparing for a coaching session with [team member / role].
Their goal: [what they're trying to achieve — skill / career / challenge]
Background: [what I know about their situation]
Coaching style I want to use: [directive / non-directive / GROW model]
Generate 10 powerful coaching questions for this session, organized by GROW model:
- Goal (2 questions): clarify what they want
- Reality (3 questions): understand current state
- Options (3 questions): explore possibilities
- Will/Way Forward (2 questions): commit to action
Also suggest what NOT to ask (questions that would make me a consultant rather than coach).
Jira / Confluence Template
Confluence — Individual Development Plan
── CONFLUENCE: INDIVIDUAL DEVELOPMENT PLAN (IDP) ────────
Name: [Team member name]
Role: [Current title] → [Aspired role in 12-18 months]
PM/Manager: [Your name]
Period: [Start] → [End]
── DEVELOPMENT AREAS ─────────────────────────────────────
Area 1: [Technical skill — e.g., system design]
Why: [business need + personal goal]
Action: [course / project / shadowing]
Timeline: [target date]
Success: [how we measure it]
Area 2: [Soft skill — e.g., stakeholder communication]
Why: [specific gap observed]
Action: [coaching / feedback / stretch assignment]
Timeline: [target date]
Success: [observable behavior change]
── CHECK-IN LOG ──────────────────────────────────────────
[Date] Progress: [what was accomplished] | Blocker: [if any]
Next review: [YYYY-MM-DD] | Overall: [ ] On track [ ] Needs adjustment