-
Notifications
You must be signed in to change notification settings - Fork 0
User stories
Mex777 edited this page Jun 4, 2024
·
2 revisions
In our game development project, we use JIRA backlog to create user stories. We use user stories to capture the essence of our features and requirements. User stories provide a non-technical description of how players will interact with different elements of the game. They focus on the player's experience, emotions, and the story conveyed through these interactions.
We organize our tasks into two main categories:
-
Creative Tasks:
- These tasks involve designing and creating visual elements for the game.
- Examples include:
- Designing props (e.g., trees, rocks, furniture)
- Creating tilesets for different environments (e.g., forest, dungeon, city)
- Crafting character sprites and animations
- Conceptualizing art style and aesthetics
-
Mechanics Tasks:
- Mechanics tasks relate to implementing gameplay features and functionality.
- Examples include:
- Implementing player movement and controls
- Creating enemy AI behavior (e.g., patrolling, chasing)
- Designing combat mechanics (e.g., attacks, abilities)
- Adding sounds
We assign priorities to our tasks to ensure efficient development:
-
P1 (Highest Priority):
- Critical features that directly impact gameplay or core functionality.
- Address these tasks first to meet essential requirements.
-
P2 (Medium Priority):
- Important features that enhance gameplay or improve user experience.
- Tackle these tasks after addressing P1 items.
-
P3 (Low Priority):
- Nice-to-have features or optimizations.
- These tasks can be deferred if necessary.
By organizing our work using user stories and priorities, we aim to create an engaging and polished game experience for our players.