Dual Jira Systems Architecture
What It Does
Designed and administering two parallel Jira systems that gave the company the ability to manage software development work and operational project work simultaneously. This was not a minor configuration task. It was an operational infrastructure build that the entire team relies on daily. Created a Scrum board for software development (sprints, stories, bugs) and a Kanban board for client operations and delivery workflows. Approximately 200 stories and tasks authored across both systems in 11 months: a volume typically managed by dedicated BAs and POs.
Key Features
- Dual Jira system design: Scrum board + Kanban board
- Clean separation of 'build work' (software) and 'operational work' (client delivery)
- ~200 stories and tasks authored across both systems in 11 months
- Workflow configurations, issue types, and board structures built from scratch
- Training program for 20+ team members across departments
- Adoption tracking with usage metrics and feedback loops
Why I Built It
The team was drowning in spreadsheets and email-based task tracking. Two distinct work types needed two distinct systems: both clean, both operational.
What I Learned
Learned that tool implementation is 20% configuration and 80% change management. The hardest part is changing behavior, not setting up software.
Skills Used & Gained
Metrics
- ~200 stories/tasks authored
- 2 parallel Jira systems (Scrum + Kanban)
- 20+ team members trained
- 3 departments onboarded
- 80%+ adoption within first month