Agile Project Work Item Screen in DevOps - 

BACKLOG (Epic, Features and User Stories)

AN EPIC 

• Create New Epic
  • DevOps > Project > Boards > Work items > Click New Work Item (select EPIC)
    • 
  • Save
    • 
  • An epic will not be assigned to any developers as such. This is basically with the Scrum Master or with the product owner.
• Add Tags to an Epic
  • 
• Reason and State
  • The state and areas are directly orientated towards one another. Changing the condition will alter the cause, as in active.
    • New: New Epic is created
    • Active: We have started working on this epic 
    • Resolved: all the features related to epic got completed.
    • Closed: acceptance, Testing has passed.
    • Removed: it has been removed from the backlog.
• Description
  • Clear definition is needed. 
    • How are we using this product page? 
    • Creating how many submodels? 
    • The client's expectation? 
    • We should describe everything simply here. 
    • A Product owner &Scrum Master must properly articulate this epic. 
    • We should know we should pick up that epic when we return after six months. We should start somewhere. What exactly? What did the client expect? We shouldn't keep asking the client the same thing.
• Discussion
  • Instagram tab like. 
  • If you use any developer's name in an comment, simply message them. by tagging its name and alerting them that we need your help or attention from you.
• Planning Tab
  • Priorities and Risk
    • All priorities are specified here from 1 to 4. Choose one if it's important. You can choose 
      • high risk and work on epics accordingly.
      • Now work item management involves development. When developing, you won't choose such priorities. So you will stick with 2 if it's a high priority with medium risk
  • Efforts- mentioned efforts in Hours or days. 
    • define and how exactly you want to measure things depends upon that business value.
  • Business value
  • Time Criticality
  • Start Date
  • Target Date
  • Classification Section
• Deployment Tab
  • Deployment
    • CI CD pipelines can be integrated here for deployment. This epic's pipelines can be integrated here. 
    • Expect the status bar. If your build is running, the status bar will appear. Also true for release pipeline development.
  • Development
    • You can add branches here. Your epic-related repository will exist here. Any developer commit, pull request, or change to that branch will show here
    • Benefit: top-level view of everything. A project owner can tell how many buildings are built from here was successful, how many changes were made, etc.
  • Related work
    • This is where you link your work items. This linking type shows child. 
    • We can will link a feature to it. Like for product page we can show
    • Its Child
    • Its sub-module. 
    • We can build relationships this way. 
    • If my epic and feature are child parents, you must continue this relationship. This will benefit you when you use this feature. 

Follow Button at Top

Click follow button to be notified or get notification of any epic changes for that.

History background

Show complete history of how this epic evolved (all creation and modification)

Links

Show connection between Epic and Features if any
Show added branches to my development area. Any modifications I make will immediately produce a hyperlink.

Attachments

Can attach all the related white papers.