SDLC Communication Game

Overview

An interactive classroom activity demonstrating the importance of communication, documentation, and proper requirements gathering in software development.

Learning Outcomes

Understanding the critical role of clear communication in software development
Appreciating the importance of proper documentation
Recognizing the value of UML and visual documentation
Experiencing common SDLC communication challenges
Learning the impact of requirement clarity on final product quality

Game Setup

Basic Rules

Students are divided into groups of 5 members
No verbal communication allowed during the exercise
No computers or mobile devices permitted
Communication only through written documentation
Time limit: 45 minutes total

Team Roles

Business Analyst (BA)
- Views the product image
- Creates written requirements and specifications
- Can create UML diagrams
- Must not show the image to others
Project Manager (PM)
- Reviews BA's documentation
- Creates project timeline
- Manages documentation flow
- Ensures requirements clarity
System Architect
- Creates system design based on BA's requirements
- Draws system architecture diagrams
- Provides technical specifications
Developer
- Creates the final product design/drawing
- Must follow architect's specifications
- Can request clarifications through PM
Quality Assurance (QA)
- Reviews final product against original requirements
- Documents discrepancies
- Creates test cases based on BA's requirements

Game Phases

Phase 1: Requirements (10 minutes)

BA studies the image and creates requirements document
Must include textual descriptions and UML diagrams
PM reviews and ensures clarity

Phase 2: Design (10 minutes)

Architect reviews requirements
Creates system design documents
PM ensures design aligns with requirements

Phase 3: Development (15 minutes)

Developer reviews design documents
Creates the product drawing
Can request clarifications through written notes

Phase 4: Testing (10 minutes)

QA reviews final product against requirements
Documents all discrepancies
Provides written feedback

Assessment Criteria

Accuracy of final product compared to original image (30%)
Quality of documentation and UML diagrams (25%)
Effectiveness of written communication (20%)
Test case coverage and defect reporting (15%)
Time management (10%)

Debrief Discussion Points

Communication challenges faced by each role
Importance of clear requirements and documentation
Value of UML in conveying design concepts
Impact of miscommunication on final product
Suggestions for improvement in real-world scenarios
Comparison of different team approaches and results

Variations

Use different types of images (UI mockups, system diagrams, etc.)
Add time pressure by reducing phase durations
Introduce requirement changes mid-development
Allow limited verbal communication in specific phases
Include multiple rounds with role rotation

Tips for Instructors

Choose images with appropriate complexity
Provide standard templates for documentation
Monitor time strictly for each phase
Take photos of final products for comparison
Encourage detailed feedback during debrief

SDLC Communication Game: The Silent Development Challenge

Overview

Learning Outcomes

Game Setup

Basic Rules

Team Roles

Game Phases

Phase 1: Requirements (10 minutes)

Phase 2: Design (10 minutes)

Phase 3: Development (15 minutes)

Phase 4: Testing (10 minutes)

Assessment Criteria

Debrief Discussion Points

Variations

Tips for Instructors