vinson-han / expense-tracker

0 stars 1 forks source link

Backend Dashboard API HTTP Request #23

Open vinson-han opened 2 months ago

vinson-han commented 2 months ago

Task Owner (Responsible): [First Name, Last Initial]

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.

Adding Backend Http Request for Dashboard(Expense, Goal, budgeted) (12 hours)

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.

Adding Backend Http Request for Dashboard(Expense, Goal, budgeted) - HIGH

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. …

Alex-is-Gonzalez commented 2 months ago

@santi-jose You will hold @vinson-han accountable for this issue