We were explaining how to set up the project itself, which describes the main use cases for Digital.ai Agility. This includes how to set up the workflow and how to manage and build a Kanban. I wanted to set up a Kanban, as I am a Kanban trainer. That is where my bias is towards Kanban. I was looking towards those capabilities where I can set a Kanban and get the team collaboration running, and how a full system can be set up. When they demoed it, they showed it, and Digital.ai helped with those key queries regarding support for this type of setup. However, after that, I couldn't personally explore it, to be frank.
My team is currently using this solution as our backlog management tool. We have both an on-prem version and a public cloud. We have some traditional software development teams that are using the on-prem version. For our cloud version, right now we have non-software teams that are experimenting using Agile.
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.
Vice President at a tech services company with 51-200 employees
Real User
2021-12-27T19:44:00Z
Dec 27, 2021
The Excel Release and Excel Deploy is part of the continuous delivery management stack and we use this to plan release automation. We also use it to standardize complex enterprise scale application deployments in complex environments, usually using virtual machines, containers and cloud infrastructure.
Enterprise Architect at Science Applications International Corporation
Real User
2021-06-09T22:58:00Z
Jun 9, 2021
We are using this solution to do the following: * Define portfolio epics. * Define strategic themes and link portfolio items to them. * Create features under portfolio epics. * Create enabler epics that encapsulate governance artifacts. * Create value streams (operational and development). * Associate portfolio items with value streams. * Roll up features and users' stories and tasks to achieve portfolio items and value streams. * Create teams and associate tasks with teams. * Assign points to user stories. * Assign hours to tasks. * Calculate the velocity of the team showing how many points they can take on in each iteration.
Enterprise business agility rests on agile planning that scales and has the flexibility needed to meet the needs of customers and the market. Digital.ai Agility enables organizations to scale up agile from the team level across the product portfolio, improve collaboration and efficiency, and deliver software that provides more value.
We were explaining how to set up the project itself, which describes the main use cases for Digital.ai Agility. This includes how to set up the workflow and how to manage and build a Kanban. I wanted to set up a Kanban, as I am a Kanban trainer. That is where my bias is towards Kanban. I was looking towards those capabilities where I can set a Kanban and get the team collaboration running, and how a full system can be set up. When they demoed it, they showed it, and Digital.ai helped with those key queries regarding support for this type of setup. However, after that, I couldn't personally explore it, to be frank.
My team is currently using this solution as our backlog management tool. We have both an on-prem version and a public cloud. We have some traditional software development teams that are using the on-prem version. For our cloud version, right now we have non-software teams that are experimenting using Agile.
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.
The Excel Release and Excel Deploy is part of the continuous delivery management stack and we use this to plan release automation. We also use it to standardize complex enterprise scale application deployments in complex environments, usually using virtual machines, containers and cloud infrastructure.
We are using this solution to do the following: * Define portfolio epics. * Define strategic themes and link portfolio items to them. * Create features under portfolio epics. * Create enabler epics that encapsulate governance artifacts. * Create value streams (operational and development). * Associate portfolio items with value streams. * Roll up features and users' stories and tasks to achieve portfolio items and value streams. * Create teams and associate tasks with teams. * Assign points to user stories. * Assign hours to tasks. * Calculate the velocity of the team showing how many points they can take on in each iteration.