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 4 Next »

Utilizing Start & End Dates

Start/end dates

How to define “start” - As scoped solidified

End as potential work done or released date

Creating Card Type Definitions & Upper Time Bounds

Common card type definitions

  • Define the smallest increment of work

    • Subtasks?

  • Add spike card

  • Story/New Feature

  • Task, no code or repeatable

    • KTLO task vs bug

  • Bugs

    • Internal vs external field or separate issue type

Investment / Capitalizable Concepts at Parent Level

Capitalizable flag at epic level

Any other investment type information you want to have

  • Tech debt, etc.

ULT-Work Categorization

  • Can be variable at parent level

Common definition and size for epics / initiatives

  • Goal of any parent is an org-wide definition

Jira Issue Workflows & Azure Devops Work Item States

Workflows: & workflow states (Jira - When is resolved) - If you’re going to add anything additional, you would add wait states

  • New

  • Product Requirements

  • Ready for refinement

  • Refined - Ready for Dev

  • In Dev

  • Waiting for code review

  • Code Review

  • Waiting for QA

  • QA

  • Pre-Release

  • Done/Released

  • No labels