Divergence is not Innovation: Using JIRA Agile Governance to Drive the Right Behaviors

25
DAVE LIMBAUGH AGILE COACH • SPECTRUM HEALTH Divergence is not Innovation Using JIRA Agile Governance to Drive the Right Behaviors

Transcript of Divergence is not Innovation: Using JIRA Agile Governance to Drive the Right Behaviors

DAVE LIMBAUGH • AGILE COACH • SPECTRUM HEALTH

Divergence is not Innovation Using JIRA Agile Governance to

Drive the Right Behaviors

Images ©2015 Colliers International, ©2012 Crosby Assoc., ©2014 kipnet.com, ©2015 therapidian.org

Agenda I n t r o d u c t i o n

O u r J I R A I n s t a l l a t i o n

T h e P r o b l e m

B e n e fi t s o f G o v e r n a n c e

O u r S o l u t i o n

S u m m a r y

Q & A

Problem JIRA can be configured many ways. Teams will diverge, which is not the same as innovating.

Solution

Benefits

Agile-experienced governance right from the start. What worked for us.

Common terminology, team member mobility, drive good Agile behaviors.

What You’ll Learn in this Session

Existing Applications

Image © 2015 Mansueto Ventures, LLC

Image © 2012 Office of the Municipality of North Perth

“With great power comes great responsibility.”!

- “Uncle Ben” Parker, 2002!

Test the rule or Ignore the rule?

Benefits of JIRA Governance

Reporting People Agile

Reports, charts, and metrics for the whole department or company.

Potential to auto-feed the PMO.

Common terminology for people switching teams and onboarding.

Enable and enforce good agile behaviors.

A JIRA Administrator …

… and backups Images © 2012 Optimus Nerd, ©2015 HalloweenCostumes.com

Multiple Environments

DEV TEST PROD

Sandbox for new add-ons, and groovy scripts

that change issues.

Open only to global admins.

Initial imports.

Experimental changes to configuration (issue

types, workflow, etc.)

Open to project teams by invitation.

No configuration changes allowed.

Open to all project teams.

Issue Type Schemes

Scrum Project Requests Sandbox

Issue types for development stories.

Test and Test Master for Zephyr.

For Request / Support/ Continuous Flow /

Kanban work.

Multiple sprints to release to production.

For personal issue tracking, non-

development teams.

Not Started In Development

Testing

Complete Code Review in Process

In Progress

In QA

In Analysis

In Process

Waiting

Backlog Ready for Build

Done

Ready for QA

Needs Code Review

In Triage Open

In UAT

UAT Done

Blocked

Stalled QA Done

Reopened

Completed

A Plethora of Statuses

Common Statuses

Single Workflow

Common, Visual Priorities

Global / Synchronized Sprints

Easier than Dates Scrum Ceremonies

All team meetings on the same day.

Good and bad!

Helps with intra-team dependencies.

“My team needs that done and tested by your

team by the start of Sprint 75.”

Naming Convention

In JIRA, sprints can span projects, and can have identical names.

“Team_Sprint_NN”

Creating a New Project

Groovy Scripts I Use • Agile boards: show all, show unmapped statuses

• Groups: show users, add to project roles, rename

•  Issues: assign sprints, change assignee/creator/issue type/reporter/resolution, create placeholder, delete

• Projects: delete, find non-viewable, find by group role, find newly-created

• Sprints: show by project, show from issues, create, update, delete, rename, close/open, etc.

• Users: find by display name, add users to roles in projects

• Weekly audit

Weekly Audit - What I Look For • Newly created projects – conformance to schemes, naming conventions.

• Resolutions not appropriate for the Issue Type.

• Sprints not following naming conventions.

• Projects with roles assigned to groups rather than individuals.

• Agile boards and their owners, and un-owned Agile boards.

• Anything that happens only occasionally and is too hard or impossible to “configure against”.

Problem JIRA can be configured many ways. Teams will diverge, which is not the same as innovating.

Solution

Benefits

Single-point, Agile-experienced governance right from the start.

Common terminology, team member mobility, drive good Agile behaviors.

JIRA Agile Governance

What Can You Do?

Administrator(s) Find L.C.D. Monitor!

Trusted, designated and empowered to govern.Agile-trained if using

Agile.

Find the Least Common Denominator and

challenge teams to adapt to it.

Eliminate divergence.

Data diverges like people diverge.

Vigilance is necessary.

Dave Limbaugh • Agi le Coach • Spectrum Health • Dave.Limbaugh@priori tyhealth.com

Thank You