Chapters
Prod [9/12]
Dev Master Class
0 0
0

We are invited to attend the Production track.

🎓 [Dev Master Class agenda]

Production & Project Management Track

How to successfully conduct a build review
LoCs, definition of 'Done' & validation steps
Top 5 Change Management principles

📝 Session #1: How to successfully conduct a team build review

Build Review Tip#1

General feel

Play together. First, get an overall impression; second, note details about:

Fun: Is the game enjoyable? Why or why not?

Engagement: Would you want to play more?

Paying Motivation: Would you buy the game or in game items? Does it fit the market?

Memorable Moments: Does anything stand out?

Confusion: What aspects were confusing?

Build Review Tip#2

Core Gameplay

Basic Actions: Are the core mechanics satisfying?

Complexity & Depth: How deep are the game mechanics?

Clarity: Are goals & rules easy to understand?

Variability: Does the game offer various playstyles?

Evolution: Do the game mechanics evolve?

Build Review Tip#3

Art & UI

Visual Appeal: Does the game have a unique art style?

Consistency: Is the visual style consistent throughout?

UI Clarity: Is the user interface intuitive?

Quality: Are the visuals polished?

Visibility: Are important elements easy to see?

Build Review Tip#4

Game Flow & Balance

Onboarding: Is the onboarding concise, instructive, and dynamic?

Guidance: Does the game effectively guide the player?

Balance: Is the game balanced fairly?

Difficulty Curve: Does the game scale with the player's skill?

Pacing: Is the pacing well-adjusted to keep engagement?

Build Review Tip#5

Player Progression

Reward System: Are the rewards satisfying?

Goal Setting: Are there clear short and long-term goals?

Progression: Can players see their growth?

Content: Does the game have enough content to keep players engaged?

Meta: What non-gameplay elements add depth?

Build Review Tip#6

Miscellaneous

Competitors: What are our USPs? How does the game stack up against similar games?

Technical Stability: Are there bugs or performance issues?

Social Interaction: Are multiplayer elements fun and secure?

Legal: Does the software infringe on any copyrights? Are there any age restrictions?

Then, make sure to prioritize feedback as a team: Rank issues by severity.

Was the Build Review session clear and helpful?

Please make sure to consult all cards.

📚 Session #2: LoCs, Definition of 'Done' and validation steps

During Production, the team needs to regularly review the build and assess the completion level of the features.
We propose 4 LEVELS of COMPLETION: LoC

0️⃣ LoC 0

The feature idea is discussed and added to the feature list (backlog).
A high level priority is set.

1️⃣ LoC 1

The feature is designed and documented, the team is aligned on its goal.
A high level assessment of the feasibity, cost and effort required to build it is done.
The critical feature dependencies are identified. Tech specs are listed.
The feature can be broken down into User Stories.

2️⃣ LoC2

1st implementation. The feature is prototyped using the target technology.
The core functionalities can be tested to prove the design and its potential.
The feature is connected to the other critical features and validated technically.
The detailed planning is available and the test plan is written.

3️⃣ LoC3

The feature is 'functionality' complete. It is connected to dependent features. It is Alpha.
A first pass of tuning is done. It can be playtested externally.
All signs & feedback elements are implemented: visuals, UI, audio...
The content can be placeholder however all elements of the feature can be tested.

4️⃣ LoC4

Development is complete. The feature is polished.
All content is implemented and final. The feature reached the quality target.
Tuning is done, most bugs have been fixed. It is ready for release.

Tip: How to write a good User Story?

When I

situation

, I want to

motivation

, so I can

expected outcome

🔀 Session #3: Change Management principles

Click on each tip to reveal a Change Management principle.

1. Embrace change early 🔄

Acknowledge change early to minimize rework.
If a gameplay mechanic is underperforming in playtests, adjusting it mid-production is easier than during closing or post-launch.
💡 Early feedback suggested that Aliens should move faster to increase the challenge. Reacting early prevents a late rework.

2. Keep the team involved and Communicate clearly 📢

Ensure all stakeholders (devs, designers, producers, QA) understand changes, why they happen, and their impact.
Involve them to gather input.
Communicate decisions clearly to avoid confusion and misalignment.
💡 We hesitated to add an end game and underestimated the difficulty tuning. Proper discussions could have prevented the last-minute rush.

3. Assess impact before acting 🧐

Analyze how the change affects scope, timeline, budget, feasibility and risks before approving it.
💡 Adding a Leaderboard late in production might have been too complex and caused delays. Good decision to cut it.

4. Document every change 📂

Maintain clear records of what changed, why, and when. It helps debugging, future iterations, and knowledge sharing.
💡 If collision calculations are tweaked or an Alien AI code change is implemented, documenting the reasoning ensures that other developers understand the modification and prevents issues in later iterations.

5. Test and iterate 🕹️

Every change should be tested thoroughly to ensure it doesn’t introduce new bugs or break existing systems.
💡 Additional fire-power is introduced late. Playtesting reveals it's too strong, leading to balance tweaks.

🎓 By implementing these best practices, developpers make sure they are aligned and optimize their development time.

Headers

🎓 [Dev Master Class agenda]

Build Review Tip#1 General feel

Build Review Tip#2 Core Gameplay

Build Review Tip#3 Art & UI

Build Review Tip#4 Game Flow & Balance

Build Review Tip#5 Player Progression

Build Review Tip#6 Miscellaneous

0️⃣ LoC 0

1️⃣ LoC 1

2️⃣ LoC2

3️⃣ LoC3

4️⃣ LoC4

Build Review Tip#1

General feel

Build Review Tip#2

Core Gameplay

Build Review Tip#3

Art & UI

Build Review Tip#4

Game Flow & Balance

Build Review Tip#5

Player Progression

Build Review Tip#6

Miscellaneous