Task Description:
Clearly describe the task, including what needs to be done and why.
Finalize Wireframing while taking into consideration our features
Focus on a cohesive layout
Provide support for backend set-up: set up schema for database
Acceptance Criteria:
Define specific criteria that must be met for the task to be considered complete. This sets clear expectations for the desired outcome.
Application is connected to Database
Team approval of wireframe
Estimation:
Provide time estimates for each task based on complexity and effort. Use story points or time units (e.g., hours) to estimate.
Finalize Wireframing: 1 hours
Set up schema for database: 3 hours
Dependencies:
Identify any dependencies on other tasks, team members, or external factors. Ensure that prerequisites are met before starting a task.
Backend is set up and able to connect with database
Team approves of final features in order to finalize wire frame
Priority:
Assign a priority level to each task based on its importance and impact on the project. Prioritize tasks within the backlog or sprint.
Finalize Wireframing: [moderate]
Set up schema for database: [high]
Task Type:
Categorize tasks based on their type (e.g., development, testing, design). This helps in planning and resource allocation.
Finalize Wireframing: Design
Set up schema for database: Developmental
Subtasks:
Break down larger tasks into smaller, manageable subtasks. This facilitates a more granular approach to tracking progress.
Finalize features we want to include in application
Figure out what models will be needed for our data
User, Expenses, etc.
Testing Requirements:
Specify testing requirements for each task, including unit tests and any necessary integration or end-to-end tests.
Sever connection to database
Schema Model compatibility with Prisma
Documentation:
Identify any documentation needs associated with the task. This may include code comments, API documentation, or end-user documentation.
Code comments
MongoDB connection strings
Definition of Done:
Clearly define what "done" means for each task. This includes meeting coding standards, passing tests, and completing documentation.
Task Owner (Responsible): Kevinn Gonzales
Task Assignee (Accountable): Vinson H., Edgar C.
Task Deadline: 05/06/2024
Task Description: Clearly describe the task, including what needs to be done and why.
Acceptance Criteria: Define specific criteria that must be met for the task to be considered complete. This sets clear expectations for the desired outcome.
Estimation: Provide time estimates for each task based on complexity and effort. Use story points or time units (e.g., hours) to estimate.
Dependencies: Identify any dependencies on other tasks, team members, or external factors. Ensure that prerequisites are met before starting a task.
Priority: Assign a priority level to each task based on its importance and impact on the project. Prioritize tasks within the backlog or sprint.
Task Type: Categorize tasks based on their type (e.g., development, testing, design). This helps in planning and resource allocation.
Subtasks: Break down larger tasks into smaller, manageable subtasks. This facilitates a more granular approach to tracking progress.
Testing Requirements: Specify testing requirements for each task, including unit tests and any necessary integration or end-to-end tests.
Documentation: Identify any documentation needs associated with the task. This may include code comments, API documentation, or end-user documentation.
Definition of Done: Clearly define what "done" means for each task. This includes meeting coding standards, passing tests, and completing documentation.
…