Basic Process The following image shows the Basic process backlog work item hierarchy. Issues and Tasks are used to track work, while Epics ...
Basic Process
The following image shows the Basic process backlog work item hierarchy. Issues and Tasks are used to track work, while Epics are used to group work under larger scenarios.
Epics:- To track significant features or requirements
Issues:- To track stories, bugs, or smaller items of work.
Tasks:- To track a smaller amount of work for which you want to track the time either in hours or days.
Agile Process
The following image shows the Agile process backlog work item hierarchy. User Stories and Tasks are used to track work, Bugs track code defects, and Epics and Features are used to group work under larger scenarios.
Epic:- To track significant business initiatives.
Feature:- To track specific applications or sets of works
User Story:- To track the work that you will assign to a specific team member.
Bug:- To track code defects
Issues:- To track obstacles to progress
Test Cases:- Test cases for server-side data for a sets of steps to be tested
Scrum Process
The following image shows the Scrum process backlog work item hierarchy. Product Backlog Items and Tasks are used to track work, Bugs track code defects and Epics and Features are used to group work under larger scenarios.
CMMI Process
The following image shows the CMMI process backlog work item hierarchy. Requirements and Tasks are used to track work, Bugs track code defects, and Epics and Features are used to group work under larger scenarios.
COMMENTS