Our client uses Agility in a highly defined way, but it's not flexible. That's what we brought to the table. We handled the transition and mapping to take data from Jira and define a mapping solution in Digital.ai then push that upstream through to Clarity. Then we map the data to terminology because the hierarchies are very different between safe and agile.
They're a siloed organization, but the C-suite executives don't care, and they're not going to change that. They're unwilling to change their software, but they want reports, so they brought us in to reconcile this and push the data that they need to file their financial and forecasting reports.
Even though if, in the strictest methodology sense, it didn't make that much sense but from reporting it was able to push the data. You wouldn't normally mach, for instance, a feature to an epic. You wouldn't do that because they're not at all the same. Things like that. They took terminology from Jira and they mapped it through to Agility and then took from Agility and mapped it up to Clarity. Actually, that interface was done first, the Agility to Clarity.
Agility is highly flexible. It can do much more than what our client is doing with it. They use it in a defined way. Some at that company have a much broader knowledge of agile and SAFe, but they're given applications and a mandated way to work. We had to work within their parameters and provide an accurate transition so the data would be mapped and pushed through.
