online site builder

PRODUCER - PROJECT MANAGER - QA RESPONSIBLE

Isaac Calvís Gil

Producer

What I was responsible of

-Supervise development of Alita: Unbreakable Warrior
-Calendar tracking (control milestones & objectives times)
-Control Personal Gantt’s (daily update)
-Control Personal tasks (using hack n plan)
-Tracking Scrum Objectives
-Tracking Personal assistance
-Make builds & update respective info
-Supervise Issues & Bugs (using github issues)
-Plan testings (internals & externals)

Other tasks:
 -Warning wall
 -Falling column
 -Credit Scene
 -UI QuestLog

Starting the project 

Alita: Unbreakable Warrior, development started on Febraury 2019  and ended on June 2019. We have been working on that project 4 months.

It started when our teachers showed us the game pillars:

- Based on Cyberpunk GUNNM world (Alita original manga)

- Fast Paced Diablo-like gameplay

- 3 infinite replayable levels

Production

Our Calendar

1

4 Month of development

We had from February 2019 to June 2019 to develop the game

2

8 Deliveries

We started with a Concept Discovery, then 2 Vertical Slices, 3 Alphas, Beta & Gold

Personal Gantt

1

To be efficient with time and know dependencies with mates, we created a personal Gantt for each member from team per days, it was updated every day, so everyone can see how where him teammates. Also, it works really good to measure times and see if we arrive to objectives, it’s useful to maintain a constant work. We made a Gantt per milestone.
Gantt have 4 states: Blue (Planed), Red (didn’t arrive), Yellow (it’s done but not in build), Green (it’s done and is present in build). 

Task Tracking with Hack'n'plan

1

Board x Milestone

Every milestone have his own table

2

Metrics x User

With hack'n'plan we can know how work our team, hours spend

3

Usefull tools

We can mark categories, dependencies...

Tracking Scrum Objectives

1

Scrum distribution

First we define the scrums & they're objectives, then we decide who will form part of it

2

Commitment & other info

We can see commitment of members to decide if we can put more tasks, or we have to cut. We can see other interesting info as Estimated available Time, Assigned Time in tasks, Total Time worked.

Game Builds

1

Make Builds regularly

Normally we make a build per day, if we have a delivery we make between 2 - 5 builds

2

Build Info

Every Build have changelog, version number & other info at readme useful

Supervise Issues

1

Github Issues

We use GitHub issues tool to report bugs & thinks that can be improved

2

Only I can close Issues

I close & supervise issues

3

Diferent labels for diferent issues

We have different layers to decide what kind of issues is. Also, leads assign issues to they're departments and decide who will fix it

Plan Testings

(Internal & External)

1

Regular Internal Testings

Internal testings are regularly done when we make a build

2

External Testing

We made an external testing with students from Video games Development degree. We get excellent feedback

3

All feedback is saved

Feedback from testings is saved on project drive and bugs are reported at Issues

Other documents

1

Risc Document

I made a risc document at the start of the project, with some problems that we could finde (and we made a lot of them)

2

PostMortem

After every milestone we made a postmortem with all team.

3

Personal Avaluation

I evaluate leads and i maintain some information about working hours, commitment, deviation... for everyone team member

4

Objectives

We made a document for every milestone where we put the objectives and distribute them on scrums

Other Tasks

Warning Wall

Model / Texture / Scripts / Prefab

1

Warning Wall

Warning wall is a prop that you can kick & interact with it with physics

QuestLog

1

QuestLog

It's a part of UI where you can see the quest you have to do in every moment

Credits Scene

1

Credits Scene

Credits scene where you can see all members that have worked on that project

Alita Unbreakable Warrior