Skip to content
Back to skills

825 Real World Scenario C4c829d4

ASecurity

Let's see how all 6 expert skills collaborate on a real project: **"Adding Social Login to Mobile App"**

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 11, 2026
businessgoapibackendsecurityperformancedocumentation

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 825-real_world_scenario_c4c829d4 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 825 Real World Scenario C4c829d4?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 825 Real World Scenario C4c829d4
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-825-real-world-scenario-c4c829d4/badge)](https://www.skillsdirectory.com/skills/tools-only-825-real-world-scenario-c4c829d4)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# 🎬 REAL-WORLD USAGE SCENARIO
## How the 6 Expert Skills Work Together

---

## πŸ“– Scenario: Launching a New Mobile App Feature

Let's see how all 6 expert skills collaborate on a real project: **"Adding Social Login to Mobile App"**

---

## 🎯 PHASE 1: PROJECT INITIATION

### **Senior PM Takes Lead**

**Action**: Strategic Planning & Stakeholder Alignment

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SENIOR PM                               β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Gather business requirements         β”‚
β”‚ βœ“ Define project scope & objectives    β”‚
β”‚ βœ“ Identify stakeholders (C-suite, Eng) β”‚
β”‚ βœ“ Develop project charter              β”‚
β”‚ βœ“ Create RACI matrix                   β”‚
β”‚ βœ“ Budget: $50K, Timeline: 8 weeks      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: Project Charter Complete
           β–Ό
```

**Handoff Package to Scrum Master**:
- βœ… Project scope: Social login (Google, Apple, Facebook)
- βœ… Success criteria: 80% adoption in 3 months
- βœ… Team: 2 mobile devs, 1 backend dev, 1 QA
- βœ… Sprint cadence: 2-week sprints

---

## βš™οΈ PHASE 2: SYSTEM SETUP

### **Atlassian Admin Provisions Access**

**Action**: User & System Setup

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ ATLASSIAN ADMIN                         β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Create Jira project: SOCIAL-LOGIN    β”‚
β”‚ βœ“ Provision user access for team       β”‚
β”‚ βœ“ Set up permissions (team + stakeholders) β”‚
β”‚ βœ“ Configure SSO for new contractors    β”‚
β”‚ βœ“ Create team groups                   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: System Ready
           β–Ό
```

### **Jira Expert Configures Project**

**Action**: Technical Setup

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ JIRA EXPERT                             β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Create project: SOCIAL-LOGIN         β”‚
β”‚ βœ“ Configure workflow: To Do β†’ Dev β†’    β”‚
β”‚   Code Review β†’ QA β†’ Done              β”‚
β”‚ βœ“ Set up custom fields:                β”‚
β”‚   - Platform (iOS/Android/Backend)     β”‚
β”‚   - Story Points                       β”‚
β”‚   - Sprint                             β”‚
β”‚ βœ“ Create Scrum board                   β”‚
β”‚ βœ“ Set up automation: auto-assign QA    β”‚
β”‚ βœ“ Build dashboard for metrics          β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: Jira Project Ready
           β–Ό
```

### **Confluence Expert Creates Documentation Space**

**Action**: Knowledge Base Setup

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ CONFLUENCE EXPERT                       β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Create space: Social Login Project   β”‚
β”‚ βœ“ Set up page structure:               β”‚
β”‚   - Overview                           β”‚
β”‚   - Technical Specs                    β”‚
β”‚   - API Documentation                  β”‚
β”‚   - Meeting Notes                      β”‚
β”‚   - Sprint Retrospectives              β”‚
β”‚ βœ“ Configure permissions                β”‚
β”‚ βœ“ Link Jira project to Confluence      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: Documentation Ready
           β–Ό
```

### **Template Creator Builds Standard Templates**

**Action**: Create Reusable Content

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ TEMPLATE CREATOR                        β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Create Jira issue templates:         β”‚
β”‚   - User Story Template                β”‚
β”‚   - Bug Report Template                β”‚
β”‚   - Spike Template                     β”‚
β”‚ βœ“ Create Confluence templates:         β”‚
β”‚   - Sprint Planning Template           β”‚
β”‚   - Sprint Retrospective Template      β”‚
β”‚   - Technical Design Doc Template      β”‚
β”‚   - API Integration Guide Template     β”‚
β”‚ βœ“ Deploy to project space              β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: Templates Ready
           β–Ό
```

---

## πŸƒ PHASE 3: SPRINT EXECUTION (Sprint 1)

### **Scrum Master Facilitates Sprint Planning**

**Action**: Sprint 1 Planning

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SCRUM MASTER                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Facilitate sprint planning meeting   β”‚
β”‚ βœ“ Define Sprint 1 goal:                β”‚
β”‚   "Complete Google OAuth integration"  β”‚
β”‚ βœ“ Team estimates stories:              β”‚
β”‚   - SOCIAL-1: Google OAuth Backend (8) β”‚
β”‚   - SOCIAL-2: Google OAuth iOS (5)     β”‚
β”‚   - SOCIAL-3: Google OAuth Android (5) β”‚
β”‚   - SOCIAL-4: QA Test Plan (3)         β”‚
β”‚ βœ“ Total: 21 points (capacity: 20)     β”‚
β”‚ βœ“ Create sprint in Jira                β”‚
β”‚ βœ“ Document in Confluence               β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ USES: Jira Expert for board config
           β”‚ USES: Confluence Expert for sprint doc
           β”‚ USES: Template Creator for planning template
           β–Ό
```

**Requests to Other Skills**:

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ TO: Jira Expert                β”‚
β”‚ REQUEST: Create Sprint 1       β”‚
β”‚ RESPONSE: Sprint created βœ…    β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ TO: Confluence Expert          β”‚
β”‚ REQUEST: Create sprint planningβ”‚
β”‚          page from template    β”‚
β”‚ RESPONSE: Page created βœ…      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
```

### **Daily Standups (Week 1)**

**Scrum Master Runs Daily Standups**

```
Day 1-5: Daily Standups
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SCRUM MASTER                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Day 1: βœ“ All stories in progress       β”‚
β”‚ Day 2: βœ“ Backend 50% complete          β”‚
β”‚ Day 3: ⚠️ BLOCKER: OAuth API keys      β”‚
β”‚        needed (escalate to Senior PM)  β”‚
β”‚ Day 4: βœ“ Blocker resolved              β”‚
β”‚ Day 5: βœ“ Backend complete, code review β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ ESCALATION on Day 3
           β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SENIOR PM                               β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ ⚑ BLOCKER ESCALATION                   β”‚
β”‚ Issue: OAuth API keys needed           β”‚
β”‚ Action: Contact stakeholders           β”‚
β”‚ Resolution: Keys provided same day     β”‚
β”‚ Update: Scrum Master + team            β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
```

---

## πŸ“Š PHASE 4: SPRINT REVIEW & RETROSPECTIVE

### **Sprint Review (End of Sprint 1)**

**Scrum Master Facilitates Demo**

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SCRUM MASTER                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Facilitate sprint review              β”‚
β”‚ βœ“ Demo completed features:             β”‚
β”‚   - Google OAuth working on all        β”‚
β”‚     platforms                          β”‚
β”‚ βœ“ Gather stakeholder feedback          β”‚
β”‚ βœ“ Velocity: 20/21 points (95%)        β”‚
β”‚ βœ“ Document feedback in Confluence      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ USES: Confluence Expert to doc feedback
           β–Ό
```

### **Sprint Retrospective**

**Scrum Master Facilitates Retro**

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SCRUM MASTER                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Facilitate retrospective              β”‚
β”‚ βœ“ What went well:                       β”‚
β”‚   - Great collaboration                β”‚
β”‚   - Quick blocker resolution           β”‚
β”‚ βœ“ What didn't go well:                 β”‚
β”‚   - OAuth keys delay                   β”‚
β”‚ βœ“ Action items:                        β”‚
β”‚   - Pre-request credentials (Senior PM)β”‚
β”‚   - Better API key process (Admin)    β”‚
β”‚ βœ“ Document in Confluence               β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ HANDOFF: Action items to Senior PM
           β”‚ USES: Template Creator's retro template
           β–Ό
```

---

## πŸ“ˆ PHASE 5: MID-PROJECT REPORTING

### **Senior PM Creates Executive Report**

**Action**: Stakeholder Reporting (Week 4)

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SENIOR PM                               β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Gather metrics from Scrum Master:    β”‚
β”‚   - Velocity: 20, 22 (trending up)     β”‚
β”‚   - Stories completed: 8/10            β”‚
β”‚   - Sprint health: Green               β”‚
β”‚ βœ“ Pull cross-project data from Jira    β”‚
β”‚ βœ“ Create executive summary:            β”‚
β”‚   - Status: On track                   β”‚
β”‚   - Budget: $25K spent / $50K          β”‚
β”‚   - Timeline: Week 4 / 8               β”‚
β”‚   - Risk: Low                          β”‚
β”‚ βœ“ Present to C-suite                   β”‚
β”‚ βœ“ Document in Confluence               β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ USES: Jira Expert for metrics
           β”‚ USES: Confluence Expert for report
           β–Ό
```

---

## 🎯 PHASE 6: PROJECT COMPLETION

### **Sprint 4: Final Sprint**

**Final Integration & Launch**

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SCRUM MASTER                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Sprint 4 planning                    β”‚
β”‚ βœ“ Final stories:                       β”‚
β”‚   - SOCIAL-20: Production deployment   β”‚
β”‚   - SOCIAL-21: User documentation      β”‚
β”‚   - SOCIAL-22: Analytics setup         β”‚
β”‚ βœ“ All stories completed                β”‚
β”‚ βœ“ Sprint review with stakeholders      β”‚
β”‚ βœ“ Final retrospective                  β”‚
β”‚ βœ“ Project closure                      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
```

### **Senior PM Project Closure**

**Action**: Post-Project Analysis

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SENIOR PM                               β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ“ Project metrics:                     β”‚
β”‚   - Timeline: 8 weeks (on time)        β”‚
β”‚   - Budget: $48K / $50K (96%)          β”‚
β”‚   - Scope: 100% delivered              β”‚
β”‚   - Team velocity: Avg 21 points       β”‚
β”‚ βœ“ Post-project review                  β”‚
β”‚ βœ“ Lessons learned documentation        β”‚
β”‚ βœ“ Success metrics tracking setup       β”‚
β”‚ βœ“ Archive project in Confluence        β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ USES: All experts for final documentation
           β–Ό
```

---

## πŸ† FINAL OUTCOMES

### **Success Metrics (3 Months Post-Launch)**

```
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ RESULTS                                 β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ… 82% user adoption (target: 80%)     β”‚
β”‚ βœ… 95% successful auth rate            β”‚
β”‚ βœ… 0 critical bugs                     β”‚
β”‚ βœ… Stakeholder satisfaction: 9/10      β”‚
β”‚ βœ… Team velocity improved 15%          β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
```

---

## πŸ”„ SKILL INTERACTION SUMMARY

### **How Each Skill Contributed**

**Senior PM** (Strategic)
- Project initiation & charter
- Stakeholder management
- Executive reporting
- Budget oversight
- Blocker escalation resolution
- Project closure

**Scrum Master** (Execution)
- Sprint planning (4 sprints)
- Daily standups (40 standups)
- Sprint reviews (4 reviews)
- Retrospectives (4 retros)
- Impediment removal
- Team coaching

**Jira Expert** (Infrastructure)
- Project configuration
- Workflow setup
- Board configuration
- Automation rules
- Metrics & dashboards
- Data extraction

**Confluence Expert** (Documentation)
- Space architecture
- Meeting notes
- Technical documentation
- Sprint documentation
- Knowledge base management

**Atlassian Admin** (System)
- User provisioning
- Access management
- System configuration
- Security compliance
- Integration support

**Template Creator** (Standards)
- Sprint planning templates
- Retrospective templates
- Technical doc templates
- User story templates
- Bug report templates

---

## πŸ’‘ KEY COLLABORATION POINTS

### **Most Frequent Handoffs**

1. **Scrum Master ↔ Jira Expert** (Daily)
   - Sprint board updates
   - Issue status changes
   - Velocity tracking

2. **Scrum Master ↔ Confluence Expert** (Weekly)
   - Sprint documentation
   - Meeting notes
   - Retrospective pages

3. **Senior PM ↔ Scrum Master** (Weekly)
   - Status updates
   - Blocker escalations
   - Velocity trends

4. **Template Creator β†’ All** (As needed)
   - Provide standardized templates
   - Update existing templates

5. **Atlassian Admin β†’ All** (As needed)
   - User access
   - System support
   - Integration help

---

## 🎬 CONCLUSION

This scenario demonstrates:

βœ… **Clear Separation**: Each expert has distinct responsibilities
βœ… **Seamless Handoffs**: Information flows smoothly between roles
βœ… **No Fluff**: All actions are practical and necessary
βœ… **MCP Integration**: All tools connected via Atlassian MCP
βœ… **Real-World Application**: Production-ready workflows

**The 6 expert skills work together as a cohesive, world-class team to deliver projects successfully from inception to completion.**

---

**Scenario Duration**: 8 weeks
**Team Size**: 4 people
**Skills Used**: All 6
**Success Rate**: 100%
**Budget Performance**: 96%
**Timeline Performance**: 100%

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.