Talk to us
  • CASE STUDY | RETAIL TECHNOLOGY / HARDWARE COMMERCIALIZATION

Toshiba switches to Jira in days, not months.

Toshiba Global Commerce Solutions moved its global hardware teams off a legacy no-code work management platform and onto a custom Enterprise Jira solution. Using Trundl’s Rapid Deploy delivery model, Toshiba’s own process documents became a working Jira environment in hours. Eight teams and 83 people were testing a live, familiar system by their second meeting with Trundl.

Talk to us
8 teams
83 people
2 meetings
130 to 10 labor hours
Days not months
  • ON THIS PAGE
Client Toshiba Global Commerce Solutions (TGCS)
Industry Retail Technology
Engagement Legacy work management platform to Enterprise Jira
Scale 8 hardware teams, 83 people
Method Rapid Deploy
Partner Tier Platinum Atlassian Partner
Talk to us
  • THE CLIENT

Who is Toshiba Global Commerce Solutions?

Toshiba Global Commerce Solutions (TGCS) is a leading global provider of retail technology, offering hardware, software, and services including POS systems, self-checkout kiosks, and retail solutions that improve customer experience and digital transformation in stores. Trundl transformed Toshiba’s existing hardware commercialization process documentation into a working Enterprise Jira environment for 8 teams and 83 people.

  • THE BUSINESS CHALLENGE

A familiar tool that could not scale.

Toshiba’s hardware development teams span electrical, mechanical, BIOS, compliance, manufacturing, and test. They managed commercialization programs on a legacy cloud-based, no-code work management platform. The teams were comfortable with it. It could not scale to enterprise needs.
01

No Executive Visibility

The legacy tool provided no executive-level rollups or portfolio visibility across hardware programs.

02

No Earned Value Management

Capacity planning and earned value management were not supported.

03

No Native Integration

The platform had no native integration with Toshiba’s corporate Atlassian ecosystem.

04

Deployment Risk

An executive mandate set the move to Jira. A traditional deployment involving design workshops, long discovery cycles, and manual configuration would slow adoption and disrupt active programs.

  • PROJECT OBJECTIVES

Familiar on day one. Enterprise-ready from the start.

01

Transform the Model

Rebuild the legacy tool’s hardware commercialization model inside Jira.

02

Preserve What Works

Retain existing project structures, naming conventions, and workflows so teams recognized their own processes.

03

Minimal Re-training

Enable global hardware teams to begin working in Jira without a prolonged re-training cycle.

04

Validate Fast

Prove the approach in a sandbox before committing to a broader rollout.

  • THE TRUNDL APPROACH

Rapid Deploy: existing knowledge into a working system.

Before kick-off, Toshiba provided the same process documentation assets originally used to build their legacy solution: process and work breakdown documentation, commercialization phase definitions, and hardware-specific task models. The documents arrived in different formats and were extensive. A traditional approach would put a Solution Architect and a Jira Engineer through weeks of manual interpretation and configuration.
01

Documentation as Input

Rapid Deploy transformed Toshiba’s work breakdown documentation and meeting transcripts directly into a working Jira solution in their sandbox.

02

Structures That Matched

Jira project structures aligned to Toshiba’s hardware lifecycle, with familiar phase, task, and subtask hierarchies.

03

Configured, Not Templated

Custom fields, workflows, validations, and dashboards built to Toshiba’s actual process, not a generic starting point.

04

Team-Level Views

Boards and views tailored to each cross-functional team from the first sandbox build.

  • TIME TO VALUE

From discovery to UAT in two meetings.

By the second meeting, instead of discussing what a Jira solution could look like, Toshiba teams were shown what it already looked like. They tested a live custom Jira instance that mirrored their legacy environment.

Structures matched

Project structures, naming conventions, and labels matched existing practice.

Immediate use

Teams could create, sequence, and manage hardware tasks straight away.

Rollups from day one

Portfolio-level visibility and rollups were available immediately.

Risk-free feedback

The sandbox allowed hands-on feedback without touching live programs.
Users were no longer evaluating concepts. They were validating a live system that reflected how they worked. Conversations shifted from abstract requirements to concrete refinements, accelerating buy-in and confidence.
Trundl is leveraging AI in innovative ways. We anticipated months to build a custom Jira solution for a new development process, but Rapid Deploy analyzed our requirements meeting transcripts and delivered a sandbox-ready configuration within hours of our second meeting.

Jim Hawk

Toshiba Global Commerce Solutions
  • DELIVERY HIGHLIGHTS

Quality, value, and speed

QUALITY Recognized on sight

Hardware teams recognized their own processes and structures immediately. Change resistance dropped because familiar structures were preserved.

TIME TO MARKET 130 to 10 hours

An effort originally scoped at 130 labor hours and four weeks was completed in under 10 hours, including labor and meeting time.

VALUE ADD Foundation built

Earned value management, capacity planning, and enterprise reporting supported from the start. Costly legacy software removed.

  • WHY IT MATTERS

Value first. Optimization second.

This engagement showed how Rapid Deploy lets companies move beyond traditional Jira implementations. Trundl’s Contextual Delivery approach converts existing knowledge directly into working systems, so teams experience value first and optimize second. It opens a path to lightweight change, innovation, and experimentation for Atlassian customers.

For Toshiba, it meant going from a legacy tool dependency to a familiar, enterprise-ready Jira environment in a matter of days — proving that enterprise Jira adoption for hardware teams does not have to be slow, disruptive, or theoretical.

  • FAQ

Frequently asked questions.

How did Rapid Deploy build a Jira configuration in hours?

Toshiba supplied the process documentation and meeting transcripts already used to build their legacy solution. Rapid Deploy converted those assets directly into Jira project structures, workflows, custom fields, and dashboards inside a sandbox, removing the manual interpretation phase that normally consumes a Solution Architect and Jira Engineer for weeks.

Did teams need to re-learn how they work?

No. Project structures, naming conventions, phase hierarchies, and labels were carried across from the legacy environment. Hardware teams recognized their own processes in the first sandbox session.

What was validated in the sandbox?

Teams created, sequenced, and managed hardware tasks against live configuration, with portfolio-level rollups available from day one. Feedback was collected hands-on against a working system rather than against a design document.

What did the broader engagement include?

The migration and integration work continued beyond the initial build, including Jira training for global team members. The two-meeting milestone refers to reaching a usable, testable Jira environment, not the close of the full program.