Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »



Inform proper stakeholder of any changes (ex. schema changes, etc..) that impact their system

Definition of Ready    |   Ready Enough


General

  • Inform the proper stakeholders for any upcoming changes that affect their systems or business 
  • All work-items must have Business Value section written if applicable
  • Must have approval from PO & Business Stakeholders prior to placing the work-item into the Sprint Backlog
  • Must have approval from Development Team prior to placing the work-item into the Sprint Backlog (excludes Task work-items)
  • Update ODE user guide if applicable: https://github.com/usdot-jpo-ode/jpo-odedocs/JPO_ODE_UserGuide.docx 

User-Stories

  • ODE's User-Story Template is used as the basis to create the story
  • User-Story has a Story/Conversation piece written (as a ... i want .. so that)
  • User-Story Acceptance Criteria written
  • User-Story is Sized

Epics

  • ODE's Epic Template is used as the basis to create the epic

Enablers

  • ODE's Enabler Template is used as the basis to create the enabler

Bugs

  • ODE's Bug Template is used as the basis to create the bug ticket

Spikes

  • ODE's Spike Template is used as the basis to create the spike



  • Action item for tmorsi
  • link items to actual template 
  • No labels