![]() ![]() Task: Reduce latency to improve character movement.Subtask: Create a visual for joystick configuration in the options menu.Subtask: Implement input mapping for character movement.Subtask: Map game mechanics to joystick inputs.Story: As a player, I want to use a joystick to control my character.In this example, the epic encompasses the story of adding joystick support, as well other stories, tasks, and bugs in an overall initiative. In the backlog, you can filter by issues belonging to a single epic. As the name implies, epics usually represent a significant deliverable. Epicįinally, an epic is a parent issue that groups stories, tasks, and bugs together to capture a large, holistic body of work. However, each subtask has its own issue key and can be moved through boards independently. Create a visual for joystick configuration in the options menuĪ subtask can only be created under a parent issue.Implement input mapping for character movement.In the above story of adding support for an input device, the following subtasks may be completed by different team members: Since they are written for the person working on the task, subtasks can be more technical than their parent issues. ![]() Example: Character sometimes moves backward when pushing the joystick forwardĪ subtask is the child of another issue, and is used to break down stories, tasks, or bugs into individually manageable pieces of work.This enables the team do things like filter by bugs in the backlog or draft reports on the number of bugs fixed per week. By classifying bugs as their own issue type, we can differentiate the work they require from other issues. While tasks can generally be completed by one team member, they may also be broken down into individually manageable subtasks. In this case the task involves updating a core function of the game rather than a user feature. Example: Reduce latency to improve character movement.A task contains a more detailed and technical description of the particular work item. Tasks are work items that are not directly related to a user requirement but still must be completed, like the upgrading of a server, the coding of a function, or even the ordering of a pizza for the team. To solve this issue, it may be necessary to assign several smaller work items to individual teammates as subtasks. The player is the user of the game, and in this story, the support for an input device is required. Example: As a player, I want to use a joystick to control my character (or “Add joystick support”).Stories should be defined using non-technical language so anyone involved in the project can understand. ![]() Say we’re on a team of game developers, and we’re working on the latest AAA title.Ī story (or user story) is a feature or requirement from the user’s perspective. How do they relate to each other, and how are they used? Let’s put it into context with an example. The standard issue types in Jira are story, task, bug, subtask, and epic.
0 Comments
Leave a Reply. |