November 3, 2015 at 12:23

Another methodology: Stakhanov



    General principles


    1. Tasks are created and written for the convenience of performers.
    2. The result of the work of gamedisaners are complete and understandable tasks even for beginners.
    3. Performers read assignments and change their status. (they write code, not tasks)
    4. Long hanging tasks - are deleted (it will be necessary - we will start again)




    General Description Style


    1. Team: what, to whom and when to do. There should not be any ambiguities and conjectures.
    2. Only complete phrases. With a detailed (step-by-step) description of actions.
    3. A phrase taken out of context should remain meaningful.
    4. All parameters must have digital values ​​(number of elements, image size, line length)
    5. All lists should be numbered (easier to do Check List)
    6. Long lists should be divided into semantic groups of 3 elements
    7. The inscriptions in the figures and in the text should match verbatim. If they do not match, then these are different inscriptions.
    8. Close attention is paid to errors and extreme situations (incorrect characters, long lines, loss of connection, incorrect time, fast and erratic tapas)


    Functional Description


    1. how to start / call it?
    2. full list of all answer options
    3. full list of reactions to each action option
    4. a detailed list of all errors that may occur
    5. description of extreme situations (long lines, loss of communication, etc.)
    6. how to close it, where to go after it?


    Job types


    Introducing New Features

    1. A big task is created, which is assigned to the game designer (responsible for introducing the functionality)
    2. The game designer breaks the functionality into subtasks and paints each of them.
    3. Any subtask must be completed by one person in less than one day.
    4. Including tasks such as estimating deadlines, compiling a list, researching technologies, etc.

    Short task:

    1. link to general (big task)
    2. if elements or links to other tasks are mentioned in the task, they must be indicated
    3. any list should be numbered
    4. long lists should be divided into triples (grouping of elements within the meaning)
    5. a short task should not contain links to external documents or pictures: everything necessary should be indicated in the task itself (external sources may disappear)

    Correction task:

    1. How to reproduce (quick way) - you may need a test level or something else.
    2. What exactly is working incorrectly
    3. How it should work correctly (how to check that the bug is fixed)


    Members



    Producer

    1. assigns tasks to a game designer (in Design Notes status)
    2. views and comments on tasks scheduled by the game designer
    3. subscribes to tasks scheduled by the game designer to track them
    4. checks the Waiting Other task list and intervenes if help is needed

    Game designer

    1. schedules tasks (short tasks of no more than one day in the form of subtasks) set by the producer
    2. Coordinates the painted design with the producer and the main programmer.
    3. having finally completed the task and having agreed, it changes the status of Design Notes -> Tech task
    4. selects the Resolved task and verifies its execution
    5. if the conditions of the task are not fulfilled, the task is rediscovered
    6. if the conditions are met, the task is closed. Resolved -> Closed
    7. in case of new conditions (and now the arrow to the right, quickly here) - a new task is created with a link to the previous one.
    8. If all subtasks (painted by the game designer) are closed, you can close the global task set by the producer.

    Programmer

    1. when the current task is completed, closes it and starts choosing a new one
    2. first you need to check the pending tasks Waiting Other - can they be continued?
    3. if it was not possible to find among the deferred ones, we select new ones only among the Tech Task with the highest priority assigned to the programmer.
    4. if there are more than 3 such tasks - he asks the game designer to rank the tasks by priority (High - no more than 3)
    5. the selected task is being studied
    6. if the task is incomplete or incomprehensibly written - it is sent back to the game designer
    7. if everything is clear - changes the status in In Progress and begins to complete the task
    8. when it becomes impossible to complete the task - Waiting Other status is set
    9. the task is postponed - this is a signal for game designers and producers about the need to help.
    10. if the task is completed - set the status to Resolved (can be changed through a comment in the repository commit)
    Tags:

    Also popular now: