October 22, 2023 • 12 mins
Tell us what you thought of the episode and any topics you would like us to cover!
Are you ready to master the power of prioritization in game development? Join me, your host Christopher Mifsud, for a deep conversation about the often misunderstood process of scope reduction. We'll unravel the potential hazards of overscoping, from skyrocketing budgets and postponed launches to compromising the quality of your game and overworking your team. Exploring the wisdom of 'less is more', we'll look at how embracing this philosophy can lead to more streamlined, impactful games.
I'll share practical strategies for efficient scope reduction, such as honing in on core game mechanics, adopting modular development, and the importance of continuous play testing. We'll tackle the emotional aspect of cutting cherished ideas and talk about keeping the end goal in sight. We'll even discuss the role of tools and tech in managing scope and the crucial task of effectively communicating scope reduction to stakeholders. Whether you're a seasoned veteran or fresh to game development, this episode is teeming with insights that can help you make tough calls without sacrificing your game's primary vision. Let's make hard decisions a little less hard, shall we?
Join Our DISCORD!
Wishlist Shadow City Mysteries: A Clockwork Noir on Steam!
Pre-Order Shadow City Mysteries: The Roleplaying Game on Backerkit!
Link to my FREE ebook: 5 Heroic Leadership Skills
Music by: Joey the Mad Scientist
Hit subscribe/follow and be sure to check out: https://pressstartleadership.com/
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:20):
Hey there, press starters and welcome to the
press start leadership podcast,the podcast about game changing
leadership, teaching you how toget the most out of your product
and development team and becomethe leader you were meant to be
leadership coaching andtraining for the international
game industry professional.
(00:40):
Now let me introduce you toyour host, the man, the myth,
the legend, christopher Mifsud.
Speaker 2 (00:49):
Hey there, press starters and welcome back to
another special edition of thepress start leadership podcast.
On this week's episode, we'rediscussing trimming the triumph
mastering scope, production andgame development strategies for
discerning what stays and whatgoes in video game production
for optimal results.
In the world of video gamedevelopment, there's an adage
(01:12):
that's been passed around foryears, both humorous and
sobering Kill your babies.
While the phrase mightinitially sound jarring, its
message is clear.
Sometimes you need to let go ofcherished ideas or elements to
ensure the larger projectthrives.
This process, often term scopereduction, is a crucial aspect
(01:32):
of game development, ensuringprojects remain feasible within
budget and timely.
This podcast delves deep intothe intricacies of scope
reduction, offering strategiesand insights to make these hard
decisions without compromisingthe game's core vision, the
dangers of overscoping and gameproduction.
Before we dive into the nittygritty of reducing scope, it's
(01:54):
important to understand theperils of overscoping.
First off, budget overruns.
Every additional feature orelement requires resources, from
design to testing.
Overscoping can quicklyescalate costs, potentially
making the project financiallyunviable.
Then there's delayed launches agame that's forever in
development risk becomingoutdated or losing market
(02:17):
relevance.
Think about quality compromises.
Stretching resources toaccommodate every feature might
mean each element doesn't getthe attention it deserves,
affecting the overall gamequality and team burnout.
Continual crunch time and everexpanding to-do lists can
exhaust teams, leading todecreased morale and
productivity.
(02:37):
Embracing the philosophy ofless is more, a streamlined game
with a clear focus can often bemore impactful than a sprawling
one with multipleunderdeveloped features.
Consider iconic games likeFlappy Bird or Tetris.
Their simplicity is theirstrength.
They offer engaging gameplaywithout overwhelming the player
(02:58):
with myriad features.
As a game developer, embracingthis philosophy of less is more
can be the step towardseffective scope management.
Strategies for effective scopereduction Think about how to
prioritize core game mechanics.
Identify the heart of your game, the primary mechanics that
drive gameplay.
Any feature or element thatdoesn't enhance or support this
(03:21):
core can be a candidate forelimination.
Consider modular development.
Design your game in modules orsegments.
This way, if a particularmodule is causing delays or
doesn't fit into the broadernarrative, it can be removed
without affecting the overallstructure.
Always think about continuousplay testing.
Regular play testing can offerinsights into which elements of
(03:44):
the game are truly engaging andwhich feels superfluous.
Feedback from real players canbe invaluable in determining
what to trim.
Set clear milestones.
Break down the developmentprocess into clear milestones.
If certain features are causingconsistent delays in achieving
these milestones, it might betime to reconsider their
inclusion.
Remember to embrace agiledevelopment.
(04:07):
Agile methodologies prioritizeflexibility and iterative
development.
By adopting an agile approach,developers can regularly assess
project scope and make necessaryadjustments.
Avoid feature creep at allcosts.
It's not uncommon fordevelopers to continually think
of just one more feature as thegame progresses.
(04:27):
While innovation is great,there's a need to avoid endless
additions that bloat the gamewithout substantial value
addition.
Handling the emotional aspect ofscope reduction.
For many developers, their gameis a passion project.
Each feature, character ornarrative thread might feel
deeply personal.
Hence making cuts could beemotionally challenging.
(04:48):
Detachment is key here.
While passion is vital forcreativity, there's a need for a
degree of emotional detachmentwhen evaluating game features.
Viewing decisions through thelens of overall game health
rather than personal attachmentcan aid objective decision
making.
Keep in mind that feedback is apillar.
(05:08):
Sometimes feedback from teammembers or playtesters can help
reinforce or guide scopereduction decisions.
It offers an externalperspective, free from the
biases of personal involvement.
Also, remember the largervision.
While a particular featuremight be dear, it's essential to
remember the broader gamevision If a specific element
(05:28):
doesn't align with this visionor impedes its realization.
It might be time to let go.
Document and archive justbecause a feature doesn't fit
into the current game doesn'tmean it's a bad idea.
Document and archive theseelements.
They might be perfect for asequel, dlc or an entirely
different game.
(05:49):
Engaging the team in scopereduction decisions.
A game's development is acollaborative endeavor.
Engaging the entire team inscope decisions can make the
process smoother and moreeffective.
Start by having open dialogues.
Encourage team members to voicetheir opinions and concerns.
They might offer insights thathadn't been previously
considered.
Always do departmentalcheck-ins, regularly check-in
(06:13):
with different departments artdesign testing to understand
challenges they might be facing.
Their on-ground perspective canhighlight areas ripe for scope
reduction.
Consider decentralizingdecision making.
While a project leader,director, will have the final
say, decentralizing decisionmaking to some extent can
empower team members and lead tomore informed choices.
(06:35):
And always highlight thepositives.
Ensure the team understands thereasons behind scope reduction,
be it improving game quality,ensuring timely launches or
managing resources better,understanding the balance
between vision and viability.
Every game starts with a vision,a dream of what it could become
(06:57):
.
However, as the developmentprogresses, this vision needs to
be weighed against theviability of executing it.
Keep the end goal in sight.
It's easy to become enamoredwith intricate side quests,
detailed backstories or novelmechanics.
However, always ask does itserve the primary goal of the
game?
Also, flexibility over rigidity.
(07:19):
A rigid adherence to an initialvision, even when faced with
clear signs of it beinguntenable, can lead to
significant problems down theline.
The ability to pivot, even ifit means moving away from some
original ideas, can be thedifference between success and
failure.
Leveraging tools and technologyfor efficient scope management.
(07:39):
In the digital age, there aremyriad tools and technologies
available that can assist gamedevelopers in managing and
reducing scope.
First is project managementtools.
Platforms like JIRA, trello orSANA can help in breaking down
the game development process,assigning tasks, setting
priorities and tracking progress.
(08:00):
These tools allow for visualrepresentation of the project,
making it easier to spot andaddress scope issues.
Have feedback platforms Toolslike User Voice or Canny can
co-late feedback from playtesters, beta testers or even
team members, providing a clearpicture of which features
resonate and which might beextraneous.
Consider analytics In-gameanalytics can offer data-driven
(08:24):
insights and player behavior.
Certain features or levels areconsistently skipped or not
engaged with might be anindicator that they aren't
crucial to the game experience.
Communicating scope productionto stakeholders.
While internal team alignmentis essential, it's equally
crucial to communicate scopedecisions to external
stakeholders, be it publishers,investors or even the game or
(08:46):
community.
Always consider honesty is thebest policy.
When discussing scope reduction, it's vital to be transparent
about the reasons behind suchdecisions, whether it's due to
budget constraints, timelimitations or quality concerns.
Stakeholders appreciate honesty.
Highlight the benefits, whilethe initial reaction might be
disappointment.
Highlighting the benefits ofscope reduction more refined
(09:08):
game experience, betteroptimization, quicker release
times can help in gettingstakeholders on board.
Use visuals, sometimesshowcasing a trimmed-down
version of a feature or a leveljuxtaposed against the original
can help stakeholders visualizewhy the scope was reduced.
And always keep channels open.
Regular updates and openchannels for feedback ensure
(09:31):
that stakeholders feel involvedand valued, even if they may not
agree with every decision.
We're visiting and reevaluatingpost-launch.
Scope reduction isn't just apre-launch strategy.
Post-launch is essential toreevaluate.
Remember DLCs and expansions.
Some of the features that weretrimmed might find a new lease
in life and DLCs are expansions.
(09:52):
This not only offers additionalrevenue streams, but also
satisfies fans, who might havebeen looking forward to certain
aspects.
You always have patches andupdates Based on player feedback
.
Some aspects of the game mightneed refining, expanding or even
reducing.
Post-launch patches offer anopportunity to adjust scope
based on real-world data, andthere's always sequels and
(10:13):
spin-offs, as hinted earlier.
Just because a feature didn'tfit into the current game
doesn't mean it's lost forever.
Sequels, spin-offs or even newprojects might benefit from
these archived ideas.
Final Thoughts Scope reduction,or killing your babies as it's
colloquially known, is anintegral aspect of video game
development.
It ensures that the gameremains viable and delivers on
(10:36):
its core promise withoutbecoming bogged down by
unnecessary features or bloatedambitions.
While the process can beemotionally taxing, especially
when letting go of a feature oneis deeply attached to, it's a
necessary discipline in the highstakes world of game
development.
By prioritizing, stayingflexible, leveraging tools and
maintaining open communicationchannels, game developers can
(10:57):
master the art of scopereduction, ensuring their
projects are both visionary andviable.
Alright, and that's this week'sepisode of Press Start
Leadership Podcast.
Thanks for listening and, asalways, thanks for being awesome
.
Hey there, press starters and welcome to the
press start leadership podcast,the podcast about game changing
leadership, teaching you how toget the most out of your product
and development team and becomethe leader you were meant to be
leadership coaching andtraining for the international
game industry professional.
(00:40):
Now let me introduce you toyour host, the man, the myth,
the legend, christopher Mifsud.
Speaker 2 (00:49):
Hey there, press starters and welcome back to
another special edition of thepress start leadership podcast.
On this week's episode, we'rediscussing trimming the triumph
mastering scope, production andgame development strategies for
discerning what stays and whatgoes in video game production
for optimal results.
In the world of video gamedevelopment, there's an adage
(01:12):
that's been passed around foryears, both humorous and
sobering Kill your babies.
While the phrase mightinitially sound jarring, its
message is clear.
Sometimes you need to let go ofcherished ideas or elements to
ensure the larger projectthrives.
This process, often term scopereduction, is a crucial aspect
(01:32):
of game development, ensuringprojects remain feasible within
budget and timely.
This podcast delves deep intothe intricacies of scope
reduction, offering strategiesand insights to make these hard
decisions without compromisingthe game's core vision, the
dangers of overscoping and gameproduction.
Before we dive into the nittygritty of reducing scope, it's
(01:54):
important to understand theperils of overscoping.
First off, budget overruns.
Every additional feature orelement requires resources, from
design to testing.
Overscoping can quicklyescalate costs, potentially
making the project financiallyunviable.
Then there's delayed launches agame that's forever in
development risk becomingoutdated or losing market
(02:17):
relevance.
Think about quality compromises.
Stretching resources toaccommodate every feature might
mean each element doesn't getthe attention it deserves,
affecting the overall gamequality and team burnout.
Continual crunch time and everexpanding to-do lists can
exhaust teams, leading todecreased morale and
productivity.
(02:37):
Embracing the philosophy ofless is more, a streamlined game
with a clear focus can often bemore impactful than a sprawling
one with multipleunderdeveloped features.
Consider iconic games likeFlappy Bird or Tetris.
Their simplicity is theirstrength.
They offer engaging gameplaywithout overwhelming the player
(02:58):
with myriad features.
As a game developer, embracingthis philosophy of less is more
can be the step towardseffective scope management.
Strategies for effective scopereduction Think about how to
prioritize core game mechanics.
Identify the heart of your game, the primary mechanics that
drive gameplay.
Any feature or element thatdoesn't enhance or support this
(03:21):
core can be a candidate forelimination.
Consider modular development.
Design your game in modules orsegments.
This way, if a particularmodule is causing delays or
doesn't fit into the broadernarrative, it can be removed
without affecting the overallstructure.
Always think about continuousplay testing.
Regular play testing can offerinsights into which elements of
(03:44):
the game are truly engaging andwhich feels superfluous.
Feedback from real players canbe invaluable in determining
what to trim.
Set clear milestones.
Break down the developmentprocess into clear milestones.
If certain features are causingconsistent delays in achieving
these milestones, it might betime to reconsider their
inclusion.
Remember to embrace agiledevelopment.
(04:07):
Agile methodologies prioritizeflexibility and iterative
development.
By adopting an agile approach,developers can regularly assess
project scope and make necessaryadjustments.
Avoid feature creep at allcosts.
It's not uncommon fordevelopers to continually think
of just one more feature as thegame progresses.
(04:27):
While innovation is great,there's a need to avoid endless
additions that bloat the gamewithout substantial value
addition.
Handling the emotional aspect ofscope reduction.
For many developers, their gameis a passion project.
Each feature, character ornarrative thread might feel
deeply personal.
Hence making cuts could beemotionally challenging.
(04:48):
Detachment is key here.
While passion is vital forcreativity, there's a need for a
degree of emotional detachmentwhen evaluating game features.
Viewing decisions through thelens of overall game health
rather than personal attachmentcan aid objective decision
making.
Keep in mind that feedback is apillar.
(05:08):
Sometimes feedback from teammembers or playtesters can help
reinforce or guide scopereduction decisions.
It offers an externalperspective, free from the
biases of personal involvement.
Also, remember the largervision.
While a particular featuremight be dear, it's essential to
remember the broader gamevision If a specific element
(05:28):
doesn't align with this visionor impedes its realization.
It might be time to let go.
Document and archive justbecause a feature doesn't fit
into the current game doesn'tmean it's a bad idea.
Document and archive theseelements.
They might be perfect for asequel, dlc or an entirely
different game.
(05:49):
Engaging the team in scopereduction decisions.
A game's development is acollaborative endeavor.
Engaging the entire team inscope decisions can make the
process smoother and moreeffective.
Start by having open dialogues.
Encourage team members to voicetheir opinions and concerns.
They might offer insights thathadn't been previously
considered.
Always do departmentalcheck-ins, regularly check-in
(06:13):
with different departments artdesign testing to understand
challenges they might be facing.
Their on-ground perspective canhighlight areas ripe for scope
reduction.
Consider decentralizingdecision making.
While a project leader,director, will have the final
say, decentralizing decisionmaking to some extent can
empower team members and lead tomore informed choices.
(06:35):
And always highlight thepositives.
Ensure the team understands thereasons behind scope reduction,
be it improving game quality,ensuring timely launches or
managing resources better,understanding the balance
between vision and viability.
Every game starts with a vision,a dream of what it could become
(06:57):
.
However, as the developmentprogresses, this vision needs to
be weighed against theviability of executing it.
Keep the end goal in sight.
It's easy to become enamoredwith intricate side quests,
detailed backstories or novelmechanics.
However, always ask does itserve the primary goal of the
game?
Also, flexibility over rigidity.
(07:19):
A rigid adherence to an initialvision, even when faced with
clear signs of it beinguntenable, can lead to
significant problems down theline.
The ability to pivot, even ifit means moving away from some
original ideas, can be thedifference between success and
failure.
Leveraging tools and technologyfor efficient scope management.
(07:39):
In the digital age, there aremyriad tools and technologies
available that can assist gamedevelopers in managing and
reducing scope.
First is project managementtools.
Platforms like JIRA, trello orSANA can help in breaking down
the game development process,assigning tasks, setting
priorities and tracking progress.
(08:00):
These tools allow for visualrepresentation of the project,
making it easier to spot andaddress scope issues.
Have feedback platforms Toolslike User Voice or Canny can
co-late feedback from playtesters, beta testers or even
team members, providing a clearpicture of which features
resonate and which might beextraneous.
Consider analytics In-gameanalytics can offer data-driven
(08:24):
insights and player behavior.
Certain features or levels areconsistently skipped or not
engaged with might be anindicator that they aren't
crucial to the game experience.
Communicating scope productionto stakeholders.
While internal team alignmentis essential, it's equally
crucial to communicate scopedecisions to external
stakeholders, be it publishers,investors or even the game or
(08:46):
community.
Always consider honesty is thebest policy.
When discussing scope reduction, it's vital to be transparent
about the reasons behind suchdecisions, whether it's due to
budget constraints, timelimitations or quality concerns.
Stakeholders appreciate honesty.
Highlight the benefits, whilethe initial reaction might be
disappointment.
Highlighting the benefits ofscope reduction more refined
(09:08):
game experience, betteroptimization, quicker release
times can help in gettingstakeholders on board.
Use visuals, sometimesshowcasing a trimmed-down
version of a feature or a leveljuxtaposed against the original
can help stakeholders visualizewhy the scope was reduced.
And always keep channels open.
Regular updates and openchannels for feedback ensure
(09:31):
that stakeholders feel involvedand valued, even if they may not
agree with every decision.
We're visiting and reevaluatingpost-launch.
Scope reduction isn't just apre-launch strategy.
Post-launch is essential toreevaluate.
Remember DLCs and expansions.
Some of the features that weretrimmed might find a new lease
in life and DLCs are expansions.
(09:52):
This not only offers additionalrevenue streams, but also
satisfies fans, who might havebeen looking forward to certain
aspects.
You always have patches andupdates Based on player feedback
.
Some aspects of the game mightneed refining, expanding or even
reducing.
Post-launch patches offer anopportunity to adjust scope
based on real-world data, andthere's always sequels and
(10:13):
spin-offs, as hinted earlier.
Just because a feature didn'tfit into the current game
doesn't mean it's lost forever.
Sequels, spin-offs or even newprojects might benefit from
these archived ideas.
Final Thoughts Scope reduction,or killing your babies as it's
colloquially known, is anintegral aspect of video game
development.
It ensures that the gameremains viable and delivers on
(10:36):
its core promise withoutbecoming bogged down by
unnecessary features or bloatedambitions.
While the process can beemotionally taxing, especially
when letting go of a feature oneis deeply attached to, it's a
necessary discipline in the highstakes world of game
development.
By prioritizing, stayingflexible, leveraging tools and
maintaining open communicationchannels, game developers can
(10:57):
master the art of scopereduction, ensuring their
projects are both visionary andviable.
Alright, and that's this week'sepisode of Press Start
Leadership Podcast.
Thanks for listening and, asalways, thanks for being awesome
.
Popular Podcasts
Dateline NBC
Current and classic episodes, featuring compelling true-crime mysteries, powerful documentaries and in-depth investigations. Follow now to get the latest episodes of Dateline NBC completely free, or subscribe to Dateline Premium for ad-free listening and exclusive bonus content: DatelinePremium.com
24/7 News: The Latest
The latest news in 4 minutes updated every hour, every day.
Therapy Gecko
An unlicensed lizard psychologist travels the universe talking to strangers about absolutely nothing. TO CALL THE GECKO: follow me on https://www.twitch.tv/lyleforever to get a notification for when I am taking calls. I am usually live Mondays, Wednesdays, and Fridays but lately a lot of other times too. I am a gecko.