Uploaded byJason French
Hansoft Basics
The document discusses how to set up a project in Hansoft software for game development. It describes adding resources and a new project, setting up roles like product owner and scrum master, creating a backlog of tasks with estimates, staging sprints by selecting backlog items, conducting sprint planning and daily standups, tracking progress, scoring sprints by grading completed tasks, and using velocity to estimate future releases.
More Related Content
Hansoft Basics
- 1. Hansoft Basics S et t i n g u p a p r o j e c t i n H a n s o f t f o r G a m e D e v e l o p m e n t Jason French
- 2. Who is thisguy? 13 years in the game industry Development Director for NCAA Football Section 8 - First introduced to Iterative Development Used Hansoft for 1 1/2 years Twitter: @jasonfrench http://jasonfrench.org
- 3. Who is thisguy? 13 years in the game industry Development Director for NCAA Football Section 8 - First introduced to Iterative Development Used Hansoft for 1 1/2 years Twitter: @jasonfrench http://jasonfrench.org
- 4. Why Use Hansoft? Keeptrack of a large backlog Drive an iterative development workflow Make sure release plan can be accomplished Keep track of developers
- 6. Setup Add resources tothe server, if not already added Add new project Add resources to the project Mark the resources who will own the backlog
- 7.
- 9. Backlog Everything that needsto be accomplished Estimates
- 10. Backlog Everything that needsto be accomplished Estimates
- 12. Staging Sprint Select itemsfrom backlog Stage for Sprint 1 Production Owner & Leads work together to generate list
- 14. Sprint Planning Meeting withteam to review work for Sprint Estimates given by team New task estimates entered into Hansoft Task leveling / removal Commitment from team to accomplish everything
- 15. Tracking the Sprint Team updates “work remaining” Daily Stand-up Review time left Encourage team to switch around tasks if one gets ahead / behind.
- 16. Scoring the Sprint Reviewmeeting at end of Sprint Team shows what was accomplished Grade each task (full, partial, none) Split partial tasks and add remaining to backlog
- 17. Velocity Amount of “idealdays” complete vs. real time Project amount of work that can be completed in future sprints.
- 20. Release Planning Group ofSprints Tag features to complete per release Release Burndown
- 23.