The document outlines a revised Jira workflow for documentation issue types in agile projects, incorporating an 'approved' status and multiple transitions for clarity. It emphasizes managing work in progress (WIP) to optimize productivity and reduce defect rates, allowing tech writers to efficiently handle assignments based on availability and capacity. Additionally, it suggests using a card wall for visual tracking and data collection to monitor development timelines.

1. JIRA Workflow for
Documentation Issue Types
Agile Projects

2. 2
JIRA Workflow for Documentation Issue Types (Agile Projects)

3. 3
JIRA Workflow for Documentation Issue Types (Agile Projects)
This is a redraw of the original diagram you provide adding the “Approved” status we discussed and
with all the transitions drawn in (I added the “Assigned” status over what we discussed yesterday)
• When you add in all the transitions, it gets more complex looking but it’s almost the same process.
– There are only a few transitions from any specific step and the Transition names are designed to make the
choices clear and self-documenting.
• “Available”, “In Progress” and “Assigned” Statuses: Implementing this way allows you to
– Plan Work: Instantly gauge Capacity (“In Progress”) against Demand (“Available” and “Assigned”)
– Limit Work in Progress (“WIP”): Tech Writers should not be working on too many things concurrently, overloading
increases defect rates and increases risk to delivery schedule
– Tech Writers really only ever deal with Available & Assigned to get work, In Progress when working on
something and then In Review when they are finished
How work gets picked up or assigned:
• A manager or writer can assign “Available” work based on prior experience or other reason.
• “Available” work can be picked up as a writer has capacity
• If priorities change, the work can be returned to “Available” for someone else to pickup or the writer
can return it to “Assigned” to save it for themselves to get back to later.
• You can use an Agile “card wall” for Writers to pick and put Agile on your resume!
• You can easily track the status of all work by assignee to balance work and gauge productivity
• With a small amount of work when defining the workflow, we can collect data to get info like “Days
in Development”

4. 4
JIRA Workflow for Documentation Issue Types (Agile Projects)
Tracking Progress
• You can easily track the status of all work by assignee to balance work and gauge productivity
• With a small amount of work when defining the workflow, we can collect data to get info like “Days
in Development”