At AgileCraft, our point of view is that organizations should endeavor to become agile at all levels from the engineer up to the executive. However, this isn’t always practical as organizational, cultural, and structural aspects of an enterprise usually mean that transitioning to agile is an evolution, not a revolution. During this transition process, organizations need a way to link their traditional processes to newer, agile approaches.
Today we’re excited to announce the launch of AgileCraft 9.0. Designed for organizations transitioning from traditional to agile processes at all levels of the organization, AgileCraft 9.0 helps organizations de-risk agile transformations, optimize software delivery, and gain visibility and alignment across all software development efforts regardless of the chosen methodology. It does this by enabling organization to embrace a bimodal approach to software planning and delivery, integrating both waterfall and agile development and planning methodologies into a single platform.
The core of 9.0 is a suite of features that enable “bimodal IT”. Coined by Garter in 2014, bimodal development refers to the existence of both traditional and agile development processes co-existing in the same IT organization.
For us at AgileCraft, this means two things. First we help align organizations vertically by enabling traditional strategic planning activities to happen at the executive level, and they align that strategy with agile execution.
We also allow teams at the developer, program, or portfolio level to use their method of choice to actually build the software, and provide functionality that allows higher levels to aggregate and normalize that information into a common set of executive level reports.
In the end, most organizations are a mix of the two, where annual strategic planning is done using traditional methods and the delivery teams represent a mix of agile and traditional approaches.
Key Features in Version 9 include:
- New Scorecards and Project Intake Process, allowing organizations that score, weight and rank projects in their portfolio to execute their strategic planning process
- New Capacity and Resource Planning modules, allowing PMOs and Project Managers to simultaneously model resource allocations across both waterfall and agile areas of the organization
- New Forecasting and “What If Analysis” modules, allowing users to predict delivery horizons across both waterfall and agile areas of the business
- New set of Enterprise Financial Reports allowing users to plan, measure, and report on financial aspects of the software delivery process
- New Milestone-based planning and tracking, enabling users to plan the delivery of software in a commonly understood stage-gate approach
- New Project-based dependency model, allowing portfolio managers responsible for strategic planning and roadmapping to link high-level projects, not just delivery features.
Check out the press release here.
Is your organization experiencing friction in your Agile rollout trying to align traditional and agile practices? Share you experience in the comments section below.