Scribd
Upload
48 views4 pages

Development Operations Processes

The document outlines different project states for development operations including New, Backlog, Prioritized, In Progress, On Hold, Review/Demo, and Done. Workflows are presented for moving work between the Backlog and Prioritized states as well as the In Progress, On Hold, Review/Demo, and Done states. Limitations on work in progress (WIP) are discussed for the Kanban board to help manage flow between the different states.

Uploaded by

Pooja Chander Dudeja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
48 views4 pages

Development Operations Processes

The document outlines different project states for development operations including New, Backlog, Prioritized, In Progress, On Hold, Review/Demo, and Done. Workflows are presented for moving work between the Backlog and Prioritized states as well as the In Progress, On Hold, Review/Demo, and Done states. Limitations on work in progress (WIP) are discussed for the Kanban board to help manage flow between the different states.

Uploaded by

Pooja Chander Dudeja
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Development Operations

Project States

New Backlog Prioritized In progress

This is the state that a Groomed Jiras that are Jira’s that have been Jira’s that are actively
new Jira will be in. As not scheduled for more prioritized to be being worked should
part of the backlog immediate work are completed. This state be placed into this
grooming, we will placed here. During should hold a minimal state. The Kanban
review this state. If as grooming this state will amount of tickets to board should enforce
part of review it’s be reviewed for liras to allow for the team to `Work in Progress`
determined there is not be place into focus. Roughly a limits.
enough information, a `Prioritized` weeks worth of work
comment is added for for the team with a The WIP limits need to
the submitter. The Jira small buffer. be determined. They
will remain until needed are board wide, not
information is provided. user.

On Hold Review / Demo Done

Jira’s that are Prior to a Jira being Jira’s are considered


dependent upon done it must be peer done when they’ve
outside information/ reviewed/demo’d. This been approved through
assistance will be state will hold items the review process
placed in this state. ready for review/demo. and/or the demo is
The Kanban board The team will be able completed.
should enforce `Work in visibly see things in
Progress` limits. need of review. The
Kanban board should
The WIP limits need to enforce `Work in
be determined. They Progress` limits.
are board wide, not
user. The WIP limits need to
be determined. They
are board wide, not
user.
Development Operations
Backlog Grooming
Workflow Start

Open

Required
Return to
information No
submitter
provided?

Yes

Grooming

Promote
Work requires
backlogged
prioritization?
work?

No Yes Yes

Will be priority
Prioritized
work later?

No Yes
No

Abandoned Backlog

End
Development Operations
Workflow
Start

Is there
Is there work in
No prioritized
progress?
work?

Yes
Yes

In progress Prioritized

No
Yes

Is the In Do you need Received


Progress work No information needed No
complete? from others? information?

Yes
Yes

No No

Review / Demo On Hold

Review
Yes Done
approved?

End
New Backlog Prioritized In progress On Hold Review / Demo Done

You might also like