There are 4 types of Work Items in DevOps
Define how you will be managing your work items in backlogs in real time in real time.

• Basic, 
• Scrum, 
• Agile 
• CMMi

 

 

Basic Work-item
This is solely used for namesakes, if you desire to have one. work item like a management process behind the scenes, you can surely use basics. 

It has few options. Only 3 alternatives exist.

• It had portfolio backlog, called Epic Epic is nothing but a top module. 
• Portfolio backlog / Issue After epic, as a sublevel 
• At last a task. 

When Used: If you have a one-two-person team and require work item management, behind the scenes, you can go epic or basic work item method. In actuality, you won't use them for live projects.

 

 

 

Scrum Work Item

Now scrum is more precise for managing your work items. 

The top-level and sub-level modules in scrum called as portfolio backlog. Then your backlog comes. User stories from your product backlog will be allocated to you/ scrum team.  Then the development team will go ahead and create a task for themselves.

If you're following scrum, you can sprint one or four times. So depending on how many sprints you chose, you'll complete them. 

 

Impediments: Whatever has been assigned to the scrum team in in scrum we do have a separate section where we are doing issue tracking called impediments.

Bugs: Should anything go wrong, this is where we monitor it together with it. Scrum also includes a portion for tracking defects. 

When Used:  Scrum is more commonly utilized for a small to medium scale project where you desire. If where the team prefers no sprints longer than four weeks.

 

 

 

Agile  Work item

Same as scrum, The only thing is the naming convention over here.

• In Scrum it is call Product backlog item, here we called it as user stories 
• In Scrum we call it as sprint size, In Agile we call it as iteration.
• In Scrum sprint can be max of 4 weeks, in Agile, the minimum You can take two weeks of iteration, the maximum you can go till 8 weeks of iteration.
• Issue tracking: In scrum we call it as impediments. In agile we call it as issues.

 

 

When Used:  So if you're completing some user story, any features which is which will take eventually more then 4 weeks, Go with Agile. Also Agile is mainly used for large scale projects wherein it's a big project and large scale project.

 

 

 

CMMi (capability maturity model integration)

Top 2 Parts are same, Except Naming Convention
Here we called as Requirement instead of PBI or user Story, 

The last part CMMi will help you with 

• change management.
• risk management.
• issue management.

 

When Used:  if you want some additional feature of change management, issue management and risk management,