Skip to content
Michael MancusoProduct & technology executive
Projects & case studies

Complex work.
Concrete results.

Product launches, operating-model changes, and complex AI-enabled builds. Explore the business problem, the decisions I led, and what changed.

Built with agents

Product strategy and a repository-based second brain.

Phase 3 Benefits brings eight health, commuter, and wage-law account types onto one payment card. I built a repository-based second brain—product strategy, specifications, verified facts, and agent memory—to keep AI development aligned.

Specification-driven development at platform scale.

Shared FHIR-based contracts coordinated parallel development across clinical, operational, and financial workflows.

Leadership case studies

Showing 6 of 38

Kapitus

Configured and deployed Jira Cloud at Kapitus, resulting in streamlined operations across 10 Scrum teams, precise financial tracking, and real-time reporting for improved decision-making and productivity.

01

Challenge

Kapitus needed an efficient and scalable project management solution to support its rapidly growing development teams. With 10 Scrum teams working from a single backlog, managing tasks, tracking progress, and aligning financial impacts with development efforts were critical challenges that required a robust and integrated solution.

02

Action

To address these challenges, I configured and deployed Jira Cloud, implementing a series of advanced features and integrations to enhance operational efficiency and financial tracking:

  • Jira Cloud Deployment: Configured and deployed Jira Cloud to manage project workflows, enabling seamless collaboration across 10 Scrum teams.
  • Unified Backlog and Multiple Boards: Set up a unified backlog with multiple Kanban and Scrum boards tailored to each team's needs, ensuring clear visibility and streamlined task management.
  • Automated Time Logging: Integrated plugins to automatically log time spent on tasks, simplifying the process for developers and ensuring accurate time tracking.
  • Capex and Opex Tracking: Configured Jira to differentiate between capital expenditures (Capex) and operational expenditures (Opex), allowing for precise financial management.
  • Financial Impact Estimates: Tied financial impact estimates to epics, enabling us to gauge the potential business impact of each release. Post-release, we measured actual impacts to validate and refine our estimates.
  • Automated Reporting: Utilized a plugin to generate real-time presentations for stakeholders and the executive steering committee, eliminating the need for manual deck creation and ensuring up-to-date information was always available.
03

Results

The implementation of Jira Cloud and its advanced configurations led to significant improvements in project management and financial oversight:

  • Streamlined Operations: Unified backlog and tailored boards facilitated better coordination and task management across 10 Scrum teams, enhancing overall productivity.
  • Accurate Financial Tracking: Automated time logging and Capex/Opex differentiation ensured precise tracking of development costs and financial impacts, aiding in budget management and forecasting.
  • Impact Measurement: Financial impact estimates tied to epics allowed us to predict and validate the business impact of each release, enabling proactive planning and resource allocation.
  • Real-Time Reporting: Automated reporting tools provided real-time insights for stakeholders and executives, improving transparency and decision-making without the need for manual deck preparation.

Questions

What Agile training was delivered at Kapitus?

Comprehensive Agile training was provided across the organization, including hands-on workshops, role-specific coaching, and ongoing mentorship to establish Scrum practices across 10 Scrum teams.

How did Jira Cloud support 10 Scrum teams working from a single backlog?

Jira Cloud was configured with a unified backlog feeding multiple Kanban and Scrum boards tailored to each team's needs, enabling clear visibility and streamlined task management across all 10 teams.

What made this Agile training different from typical workshops?

The training combined classroom workshops with hands-on application through real project work, ongoing mentorship, and role-specific coaching — ensuring practices were embedded into daily operations rather than treated as theory.

How was financial impact tied to epics in Jira?

Financial impact estimates were attached to each epic, enabling the team to predict the business value of each release. Post-release, actual impacts were measured against estimates to refine future forecasting.

How did automated time logging improve accuracy?

Jira plugins automatically logged time spent on tasks, eliminating the need for manual time entry — ensuring accurate time tracking for Capex/Opex differentiation and reducing burden on developers.

Need a leader who can
build with AI?

Let's talk about the product challenge, the team, and the outcomes you need—whether you're improving how your business runs or building something new.

Discuss your product challenge Connect on LinkedIn