1.

Account Manager (AM) closes a client and passes on a rough time to finish the game to Product
Owner (PO) and Lead Engineer (LE). AM needs to douclecheck PO and LE before proposing any
estimates.
2. PO and LE will sit together and craft estimates for the game. PO Shares estimates with client and
LE gives detailed estimates in collaboration with dev team. Keep in mind that these estimates
should not go beyond the commited timeline by AM. In case it does, PM and LE need to talk to
AM about it.
3. PO shares proposal with detailed plan with QA as well
4. PO shares plan with client and AM such that there is at max one release per month.
5. LE breaks down game into epic, then story and then subtask plan levels. Each sprint/release will
be at max 4 weeks long or 160 hours per person.
a. subtask should not be be longer than 8-12 hours.
6. LE creates SVN link and shares with team.
7. PO will add each release as a milestone with following fields:
a. Title : <Project Name> R<release number>
b. Description: brief description of the release
c. Start Date and End Date
d. Responsible: PO will add himself here
8. PO also adds necessary project details by creating a new page
9. As per LE’s break down, PO will enter tickets with following details:
a. Title
b. Description
c. Status: Always New
d. Priority
e. Milestone
f. Plan Level
10. LE assigns resources on tickets and resources enter their estimates into their relevant tickets.
11. LE or his team member will update tickets with following details:
a. Status:
i. When work starts, it will be In Progress
ii. It will be Completed on sending it to QA
b. Assigned to
c. Estimate (in hours)
d. Due Date
12. LE’s team members will update their relevant tickets with comment on ticket’s progress and will
also add worked hours field. The updations mentioned will be done whenever a task is
completed.
13. Ticket status will be as follows:
a. New: ticket is entered by PO
b. In Progress: Dev has entered estimate and started working on it
c. Completed: Dev has completed it and sent to QA. Should be marked with LE’s approval
d. Testing: QA has started testing it
e. Reopen: An issue has been reported by QA or PO
f. Fixed: QA has fixed it. Should be marked with QA lead’s approval
 g. Accepted: PO has approved it (closed)
h. Approved: work is approved by client (closed)
14. Other supporting status will be:
a. Paused: worked is paused for some reason. Reason for pause must be entered (closed)
b. Invalid: work is no longer needed to be done or was entered wrongly (closed)
c. Deferred: work has been moved forward as per PO’s or client’s intimation (closed)
15. While in QA, ideally QA resources should be updating the same tickets. We just need to confirm
whether they will be updating tickets at Epic, Story or Subtask level.
16. QA team members will update their relevant tickets with comment on ticket’s progress and will
also update worked hours field.
17. Once all tickets are marked as accepted, PO will send the release to client for review
a. If client wants to see something early, then PO can sit down with LE and discuss a plan
of delivery before the release date
18. AM needs to start pinging PO when 3-5 days are left before release date
19. If client gives any feedback it will be either categorized as bug or improvement/addition.
a. If its an issue or a bug, the relevant ticket will go to Reopen status
b. If its an improvement/addition, then it will be analyzed by PO and LE. If it requires less
than 8-16 hours per release (art + dev + QA included), then it will go back to Reopen
status.
c. If improvement/addition is taking more time (like 16 or more hours per release) then it
will be termed as out of scope and will be added in next release/sprint or at the end of
the project scope as commited with AM. If client wants to move these improvements
earlier then AM and PO will talk to client about it.
20. Tags will be as follows:
a. Spillover: depicting this ticket is from previous milestone
b. RnD: depicting this is for future technologies/integrations we plan to do
c. Training: depicting being part of the training (initial or on job)
21. To get synced up, all team members should be meeting daily in standups and twice a week with
Division head (Art, POs, LEs and QA lead only).