Scrum and Subversion Example CS 153P Session 6

Scrum Game Development Process Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Choose Tasks move from Product to Sprint 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

What we’ve Done Defined Game Project Goals Defined 1 st Sprint Goal Created a Draft Game Design Document

Next Steps Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Create a Sprint Backlog 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

Step 2. Update Product Backlog Product Backlog ◦List of tasks needed to complete our project

Creating the Product Backlog Use your agile models and game design document as reference

Example Product Backlog Tasks Create Graphics Rendering System Create Sound Playing System Create Game Logic System Define Scoring System Define Enemy Ship Classes Create Powerup System Create All Graphics using Photoshop Code Physics System Create In-Game User Interface Prepare Asset Loading System Create Main Menu Interface Record In-Game Sounds

Next Steps Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Create a Sprint Backlog 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

Sprint Goal A target that must be achieved by the end of the sprint Should have an observable result What is the next logical step? ◦What features should we tackle first in order to create a demo-able prototype? ◦What mechanic in our game do we need to prototype early to ensure it is fun? Use Product Backlog as a reference

Next Sprint Goal ◦By end of sprint, we should have been able to create a prototype that allows the player to control his ship in-game. The prototype must also have a collision and scoring system in place: when the player shoots an enemy, they must disappear and give the player a corresponding score.

In Assembla Click Milestones  Your Milestone Click ‘Mark as Completed’ Create a New Milestone ◦Specifying your new sprint goal ◦Targeting Nov. 15 as end of Sprint

Next Steps Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Create a Sprint Backlog 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

Mon. 8 Tues Wed. 0Write widget tester 4Test middle tier 4Create widget asset 0Code the widget Thurs.Task 3 16

Create Sprint Backlog Use Product Backlog and Sprint Goal as Reference Assign Tasks among group members Give an estimated number of hours ◦Planningpoker.com

Product Backlog as Reference Tasks Create Graphics Rendering System Create Sound Playing System Create Game Logic System Define Scoring System Define Enemy Ship Classes Create Powerup System Create All Graphics using Photoshop Code Physics System Create In-Game User Interface Prepare Asset Loading System Create Main Menu Interface Record In-Game Sounds

Example Sprint Backlog TaskEstimated Hours Assigned To Create Enemy Classes2Peter Create Player Class2Paul Create Collision System10Mary Create Scoring System10John Asset Loading System15Ringo Create Game Graphics20George Create Sounds15Obama

Next Steps Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Create a Sprint Backlog 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

Scrum Questions Answer the following every day:

Using Subversion - Starting Checkout your source code in a new folder Create your Flash CS3 / FlashDevelop project in the checked-out folder Commit your source code

Using Subversion - Collaborating If your teammate has committed new source, update your folder first Commit won’t work if there is source code you haven’t downloaded yet

Sprint Backlog Burndown Chart and Tickets Dropped Story Slope = Velocity Drag works against velocity

Sprint Review on Nov. 15 Steps: 1.Define Game Project Goals 2.Create/Update your Product Backlog 3.Create/Update Game Design Document 4.Define your Sprint Goal 5.Create a Sprint Backlog 6.Iterate on the Prototype until Sprint Ends 7.Sprint Review 8.If Game not Finished, Go back to Step 2

Sprint Review Also known as a Retrospective Informal Meeting Team meets for an indefinite duration of time to discuss how to improve product and process Some guide questions: ◦What are we doing now that we should continue doing for next sprint? What should we stop? ◦What went wrong? What went right? ◦Is the game fun? ◦Did we have enough time for this sprint? ◦What will we need to do / buy to ensure that we meet the next sprint’s targets? Action points should be addressed next sprint

Assignment Define Next Sprint Goal Create tickets for Sprint Backlog Upload Game into Subversion ◦Be ready to work on your checked-out projects during Saturday Lab session