Refactoring

Sprint Planning

Alpha Build

Professional teams schedule some time for code cleanup after each milestone so their code stays flexible and easy to work with. This project will give you some tips and general principles for this process, known as refactoring. With your vertical slice done and your code in good shape, this is where you’ll start down the road to alpha.

Writing Better Code

Course Introduction and Planning

Game Jams and Skilling Up

Set your goals and find your community

What is the Design Process? 

Scope

Constraints and Our Theme

Concentric Design

Why Prototype? 

Assets shouldn't be liabilities

The Stages of Game Development

Planning your project

CRC Cards

Your First Milestone: Vertical Slice

Why Agile?

Vertical Slice - Part Two

What is Playtesting?

How To Playtest

Sprint Plan

Review and Redesign

How to Release your Game

Alpha and Beyond

Bonus Content

In this project you will learn about what's ahead for you on your journey to finishing a game! You'll also get a chance to confirm that you have the right knowledge and skills to get the most out of the course, along with links to useful resources that will help you on your way. You will also learn how to equip yourself for your journey, and meet some of your fellow adventurers.

Goal Setting and Community Building

In this project you will learn about using a design process to take your idea from a broad concept into a finished, polished game, the concept of scope will help you achieve your goal of making a game, how constraints can help you create rules to keep you in scope,  and how to use the specific design process, concentric design.

The Design Process

In this project you will find out if your game idea is fun through Prototyping. You will also learn how to make a plan for assets you will use in your game – the sounds, images, models, animations and other resources that make up a game – to avoid nasty surprises later in development. 

Prototyping

In this project you will learn how to keep a sense of the big picture by dividing the game development process into stages and milestones, hit your first major milestone in the development of a game through creating a vertical slice, and learn two planning tools you can use to plot a course to a finished game. 

Milestones

Agile Development

Playtesting is more than just asking people if your game is fun. It's a structured process for collecting useful information about specific parts of your design. In this project you will learn why Playtesting helps you collect useful information on your design and how to execute the entire process. 

Playtesting

In this project you will learn how to release your game, what the next steps are after game release, and additional tips for getting to the end. 

Release your game

Lots of people start games, but it’s surprisingly hard to finish one. This course guides you through the process used by professional game makers to develop their ideas, keep their projects on track and deliver a complete, released game. 

Explore the Unity Asset Store for game toolkits and template assets that will help you quickly design and prototype your games. These resources can accelerate your development process and help you achieve your goal of releasing a polished game!

Design and Publish Your Original Game: Unity USC Games Unlocked

9b1c7937-a691-5c93-87f2-f27b6580eb0d:IJ50VM7ryBj2kIwUvpGq9n

Don't Repeat Yourself

One Class, One Job

Design Patterns and Unity Best Practices

Assignment: Sprint Plan for Playtest Build

Plan de sprint para la compilación de prueba de juego

Agustin Dominguez

Update Sprint Plan

unity_ABBB8FB9151B27AEEBC3

i'm love you guys please i wanna friends why i don't have friends :=(

safasfafsagj

Sprint plan

Arcane_Creator

I don't know what to write here. It took too much time to test, the main problem with controlling the character was that you could jump through objects by bumping into them. 

Sprint Plan for Playtest Build

kot88murmansk

I have collected the latest changes to be made in a plan divided by scenes

Silvana Di Bella

Spooky Things- weeks 2 sprint plan completed  and week 3 sprint planned

Sprint plan 3

RoaaK

Fortunately I have the playable version of the game by this time of writing.

I have fewer tasks as the development of my game progresses.

Visit https://kaelfdl.itch.io/dronk to see the game.

Dronk Sprint plan for playtest build

kaelfdl

Don_t Repeat Yourself.mp4

One Class, One Job.mp4

This tutorial will give you some best practices and general principles for code architecture and taking your first step into Playtesting. You will also create another sprint plan for the alpha you will build by the end of this project.

Unity + USC Games Unlocked

Games

Programmers have opinions about everything. This is an experienced programmer’s detailed guide to using variables well, with numerous examples. “Software is written for people to understand.” 

A beginner programmer asks for help forming good coding habits in Unity. Experts answer. “What are some good scripting habits to form? For example, is it a good idea to expose variables in your code, such as the speed of your car or the damage done by an attack?” 

A short guide to asking code questions that get answered, including a specific example. 

An even shorter guide, by one of the most prolific question-answerers online. 

A list of good practices for Unity projects, with explanations. Many are useful for beginners. 

A frequently updated list of good practices for Unity projects. Most tips are at the intermediate to advanced level, but beginners can learn from glancing over it. 

An overview of commonly used design patterns in game programming. Intermediate to advanced level. Examples are in C++ but are well explained. 

Some of the content from the previous site, rewritten in C#. 

A general guide (that is, not focused on games) to C# implementations of design patterns. Intermediate to advanced level. 

A short, specific example of a design pattern applied to Pac-Man.  

It’s time to make your next sprint plan!You’ve got two weeks of development left before the end of the course – you're getting closer to actually publishing your game and it's likely time to make some cuts so you end up with a finished game.We’re going to ask you to playtest this week's build with real players at the beginning of the next module. That doesn’t mean it needs to be finished – in fact, the opposite is true – but you will want to have something that’s ready to play.To get ready, look at your game as a player. Go ahead and show it to a friend, post it in the Connect Group or post this week's build somewhere and ask for feedback in the forums. 

What parts are working (understandable and fun)? 

If something is broken or unfinished, do you really need it, or can you use that time better by improving the core of the experience?

The instructions are the same as last week, but for your reference, they're provided below. When you’re finished you’ll turn in some form of your sprint plan.

These instructions describe the exact process that professional teams of all sizes use to manage the work of game development. It has several steps, and it looks long because each step is explained, but it should only take 5-10 minutes to do for a small project. 

You’ll use the same system you used when you made your backlog, whether that’s a spreadsheet, a to-do manager like Trello, or a dedicated system like JIRA. When you’re finished you’ll submit in some form of your sprint plan as screenshots or a video capture. 

Taking a couple of minutes to learn from your experience each week will make you a better developer. 

Get better at estimating. Look at your current sprint plan – that’s the to-do list you made last week. Observe what you did and didn’t get done. Look at the estimates of effort you made for each item. Were you able to make an accurate guess about how long the task took? If not, what was it that made the work take longer? Just stopping to think about it will make you better at estimating your work in the future. 

Recognize your hard work. You might be disappointed in your progress this week – that’s actually pretty normal. But take a moment and pat yourself on the back for what you did get done. You’ve climbed a little further toward being a game maker, and everything you did this week will be easier from now on. 

Reset. Take everything you didn’t finish and put it back in your backlog. That might mean copying and pasting in a spreadsheet or physically moving Post-It notes, depending on your system. 

Leave the room. It’s a good idea to physically stand up and leave the room, but failing that, at least close your eyes. Imagine your game in its final form. Think about where your game is currently, that is, what’s already visible in the build. Then open your eyes and return to your work station. 

Update your backlog. Look at the stories in your backlog. Based on your vision of the final game, do you notice anything missing? Is anything unnecessary or not as important as you thought? Are there any stories that could be combined or split into smaller parts? Once you’ve updated the list of stories, look at each story in turn. Ignore its current priority and whether you’ve already done work on it. How important is it, right now, to finishing your game? Update its priority accordingly. 

Look at your availability. No week is the same. Do you have doctor appointments, lunch dates, algebra tests, or meetings with your agent? Think about each day in turn and write down how many hours you will have to give to your game this week. If the answer is zero, write zero. If you plan to work all seven days, consider taking a day off in the middle so you don’t burn out. 4. 

Now that you’ve identified the most important remaining work and the time you have to spend on it, choose stories from your backlog that you will work on this week. As you copy them into this week’s plan, go ahead and give some thought to how you will implement them. Does your estimate of effort (1, 2, 4 or 8 hours) seem about right? When you’re done, make sure your total workload matches up with your actual availability this week. 


Sprint Planning

1. Don't Repeat Yourself

2. One Class, One Job

3. Design Patterns and Unity Best Practices

4. Assignment: Sprint Plan for Playtest Build

Your submission preview

Complete this Exercise