Project Overview
The IBM Payments Center led a first-of-its-kind, fully managed Check Payments transformation for a Top 100 US Retail Bank, migrating its on-premise Financial Transaction Manager (FTM) Check Services application to the IBM Cloud.
Problem Space
The program required consolidating delivery workflows across six teams — Solution Architecture, Application Development, Quality Assurance, Project Change Request, Platform, and Program — each using different sprint processes, work stages, and reporting structures. The lack of unified Jira workflows, filters, and documentation created friction across teams and limited visibility into program-wide RAID items.
Outcomes
- Delivered project-wide Jira workflows, user stories, agile reports, and custom JQL filters in 2 weeks, accelerating Phase 0 sprint completion by 25 percent
- Created 50+ documentation assets (FAQs, workflows, filters, scenarios) to upskill team members in Jira
- Developed a design-thinking session for identifying user categories, roles, and permissions
- Produced comprehensive Jira guidelines used across all delivery teams
My Role
- I administered Jira for the entire program, mastering the platform to build efficient delivery workflows.
- Conducted needs analysis with senior stakeholders across all six teams to understand their agile processes and converted these requirements into unified project workflows, user stories, agile reports, and JQL filters.
- Analyzed FTM Check product documentation and translated delivery needs into technical documentation with acceptance criteria for the QA team.
Product Lifecycle
Discovery
- Collaborated with stakeholders from architecture, development, QA, platform, and change-management teams to understand how work moved through their pipelines.
- Identified inconsistencies in workflows, blockers, and reporting structures, and gathered the requirements needed to consolidate six parallel processes into a single delivery model.
- This discovery work clarified what Jira configurations — board types, workflow stages, RAID filters, and documentation — were required to support cross-team alignment.
Design
- Designed unified workflows and built team-specific Jira boards that reflected real sprint, QA, and deployment processes.
- Created custom JQL filters to surface program-level RAID items and developed project-wide documentation that illustrated every delivery workflow.
- Designed and facilitated a session to define KeyBank-specific user roles and permissions, enabling consistent user story creation and governance across the program.
System / Architecture View
The delivery environment consisted of six team workflows that were consolidated into a single Jira architecture. I configured board columns, statuses, and transitions; built custom RAID filters pulling from all team boards; and documented delivery paths using tables and workflow diagrams
Execution & Delivery
- Delivered all Jira structures - workflows, boards, agile reports, and filters — and validated them with each delivery lead.
- Maintained project documentation, created guidelines for Jira usage, and ensured alignment across architecture, development, QA, and platform teams.
- Work snapshots (page 3–5) include the consolidated workflow, custom JQL filters, RAID dashboards, and the full documentation set used across the project.
What I Learned
I learned how to translate multi-team delivery requirements into unified workflow systems, structure large-scale Jira environments, and enable program-wide visibility through filters and documentation. I also strengthened my skills in cross-team facilitation, technical documentation, and workflow governance at scale.
Log in or sign up for Devpost to join the conversation.