Certified Jira Workflow Professional for Developers

Master the standard Jira development workflow from todo to in-progress, through code review, testing, and Po review, ending in done with cycle time, acceptance criteria, scope clarity, and transparency.

Track real time status updates on the Jira board as stories move from in progress to code review, testing, peer review, and done, using clear on hold comments for blockers.

Learn to identify, flag, and escalate blocked items in Jira to restore flow, communicate clearly, and swarm on impediments for transparent, disciplined delivery.

Prepare your Jira board before standup to enable real-time visibility of progress, blockers, dependencies, and limit work in progress, by updating tickets, validating code reviews and tests, and assigning owners.

Adopt branch naming conventions with a three-part format: type, JIRA key, and description, linking code to tickets and boosting traceability, reviews, and clarity.

Learn to write clear commit messages that state what changed and why, use present tense, link to the Jira ticket, and make one logical change per commit.

Connect pull requests to Jira tickets using the ticket key in branch names, commits, or pull request titles to automate status updates and create a single source of truth.

Transform teams into disciplined code review workflows in Jira by assigning reviewers, linking pull requests, and tracking status from code review to in-progress with defined standards and an audit trail.

Turn fragmented code reviews into a consistent, professional process by embedding a code review checklist in the Jira workflow and linking a living Confluence standards document.

Replace ambiguity in code reviews with a clear feedback and approval flow that tracks every comment to resolution using a custom Jira review status and explicit criteria.

Embed a clear testing approach and executable acceptance criteria in every JIRA story to align developers and QA, enabling early automation, reduced defects, and faster sprints.

Log defects in Jira with clear steps to reproduce and environment, link them to the original story, and apply shared severity and priority to guide triage and bug resolution.

Learn to manage test cases in Jira with story-linked tests and test subtasks, ensuring full coverage, visible handoffs between development and qa, and end-to-end traceability from requirement to result.

Define and enforce a team-wide definition of done within Jira, using a shared checklist to ensure code reviews, tests, documentation, and product owner acceptance are complete before closing a story.

Become the information hub at the center of your team's upward, lateral, outward, and inward communication, using the four directions framework to flag risks, share progress, and document decisions.

Adopt the three voices—transparency in standups, reality in sprint planning, and improvement in retrospectives—to turn your input into essential, actionable insights.

Develop better communication by identifying five common traps developers face, such as the 'I'll just handle it' mindset and jargon overload, and learn fixes to articulate impact and ownership.

Use the three questions framework at daily stand-ups to summarize completed work, today's deliverables, and blockers to boost team coordination.

Use the 2-minute rule to stand-up updates by sharing three essentials: completed work, today's deliverable, and current blockers, reducing noise and saving team time.

Learn to spot hidden blockers, use a four-step blocker statement, follow the 24-hour rule, and shift to a proactive mindset to raise blockers effectively and keep sprints on track.

Bridge the gap between technical detail and business impact by applying the TCRV framework: time, cost, risk, and value, to clearly communicate features to stakeholders.

Balance depth and high-level explanations to match your audience, decision, time, and conversation stage, avoiding depth mismatch and focusing on business impact and trade-offs.