Build a Business-Driven Application Roadmap Using an Agile Approach
Support your ongoing business objectives with a rationalized application portfolio while remaining aligned with your current and future technology needs.
- Due to application sprawl, many of today’s organizations have reached a point where they are supporting many applications that offer minimal to no business value.
- Application roadmap projects are often shelved due to the complexity of scale.
- Organizations are looking for ways to align their business priorities to current and future decisions for applications.
- Application leaders do not have an excellent understanding of their application portfolio because they lack the processes required to gather accurate and applicable information.
- Roadmaps are often shelved and left unused due to the inaccurate information they are based on.
- Aim for realization rather than perfection.The goal is to rationalize rather than to realize some perfect state and be paralyzed in the analysis.
- Keep your application assessment process light and Agile. Big-bang approaches have a hard time getting implemented. Get your initial dispositions quickly and then drill down.
- Keep your roadmap stable and nimble. Ensure that your roadmap is reliable and flexible to make ongoing adjustments.
Impact and Result
- Improve the visibility and relevance of your application roadmap by providing accurate information about your application portfolio and assessing the technical and business impacts of your disposition decisions.
- Develop a repeatable, end-to-end process that supports the creation, usage, and maintenance of an accurate and achievable application roadmap.
- Nick Spanos, Senior Management Consultant, Leading Advisory Firm
- Najeeb Saour, Experienced Consultant, Leading Advisory Firm
- Mark Cybulski, CIO, ZF North America Inc.
- Darren Courville, Principal Management Consultant, IT Works Consulting Ltd.
- Glen Notman, Associate Partner, Citihub
- JD Davis, Senior Business Consultant, Leading Financial Institution
- Geoff Temple, Application Modernization Manager, Children’s Aid Society of Toronto
- Najam Sahar, Executive Director of Corporate Business Architecture, Manitoba Public Insurance Company
- Kal (Hjouj) Salem, Principal, Capco
- Tim Gangwish, Enterprise Architect, Elavon, Inc.
Get the Complete Storyboard
See how all the steps you need to take come together, with tools and advice to help with each task on your list.Download Now
Get to Action
Start here – read the Executive Brief
Read our concise Executive Brief to find out why you should build an application roadmap using an application rationalization initiative, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.
Determine the current state of the application portfolio
Conduct an inventory collection of applications to create a holistic view of the current application portfolio and its value to the organization.
Determine application disposition
Create capability maps to determine the application disposition from both functional and technical standpoints across specified business domains.
Conduct impact analysis
Determine the disposition’s business and system impacts by assessing its business value, technical complexity, and urgency.
Prioritize and revise the application roadmap
Determine the priority of the application dispositions for rollout and optimize the application roadmap approach.
Module 1: Determine the Current State of Your Application Portfolio
- Identify the enterprise applications that are currently being used and supported by your organization.
- Assess the value and costs to keep each application in your portfolio.
Key Benefits Achieved
- Understanding of current state of application portfolio.
- Classification of enterprise applications based on maturity.
- Clear breakdown of the costs required to support the application.
|1.1||Conduct an inventory collection of all enterprise applications.||
|1.2||Document the lifecycle stage of each application being assessed.||
|1.3||Document the costs of each application being assessed.||
Module 2: Determine Application Disposition
- Identify the business processes that are supported by your applications.
- Build your application capabilities maps and dispositions.
- Identify the level of technical and functional support of each application.
Key Benefits Achieved
- Validation of the alignment of enterprise applications to business domains and functions.
- Selection of the appropriate dispositions based on your business needs, and functional and technical assessments.
|2.1||Determine business processes that assessed applications support.||
|2.2||Build application capability maps that align with business processes.||
|2.3||Determine application dispositions and the level of functional and technical support.||
Module 3: Conduct Impact Analysis
- Assess the business and technical impact of each disposition.
- State the urgency to implement each disposition.
Key Benefits Achieved
- Clear definition of your prioritization factors: business value, technical complexity, and level of urgency.
- Full understanding of the system components supporting your applications.
|3.1||Define and prioritize your application rationalization business value metrics.||
|3.2||Create a current state systems-level diagram of the applications being assessed.||
|3.3||See the technical complexity of each disposition by drawing your target state system-level diagram.||
|3.4||Calculate Business Value and Technical Complexity scores.||
|3.5||Determine the level of urgency to implement each disposition.||
Module 4: Prioritize and Revise Your Application Roadmap
- Prioritize your disposition implementations in order to build your application roadmap.
- Make the necessary changes to your application’s lifecycle stages based on your prior analysis.
- Determine how your roadmap will be communicated to executives.
- Prepare for future application roadmapping in other business domains.
Key Benefits Achieved
- Finalized and revised application roadmap that is accurate, practical, and aligned to business priorities.
- Tailored document to effectively communicate with stakeholders.
- List of next steps for roadmap initiatives in other business domains using lessons learned.
|4.1||Determine the priority of your disposition implementations.||
|4.2||Review the lifecycle stage of relevant applications based on your impact and disposition analysis.||
|4.3||Calculate the expected net benefits of your revised application roadmap.||
|4.4||Create your executive communication document.||
|4.5||Review and optimize your application roadmap approach for your next business domain.||
Create a Horizontally Optimized SDLC to Better Meet Business Demands
Take a Holistic View to Optimize Release Management
Choose the Right Development Platform for Enterprise Mobile Applications
Develop Enterprise Mobile Applications With Realistic and Relevant Performance
Stay on Top of Today’s and Tomorrow’s Mobile App Trends
Make Development Teams Leaner and Improve Time-to-Release in Five Steps
Strengthen the SSDLC for Enterprise Mobile Applications
Use DevOps to Respond Faster to End Customers
Modernize Your Corporate Website to Drive Business Value
Implement Agile Practices That Work
Enable Organization-Wide Collaboration by Scaling Agile
Spread Best Practices With an Agile Center of Excellence
Optimize Existing Applications for Security in an Untrusted World
Choose the Right Tools for Big Data Development
Optimize the Application Maintenance Estimation (AME) Process
Use PaaS to Decrease Ongoing Application Maintenance Costs
Develop APIs That Work Properly for the Organization
Enter Into Mobile Development Without Confusion and Frustration
Reduce Churn and Improve an Existing Software Development Practice
Vendor Landscape: Application Development Tools
Choose a Mobile Development Strategy
Drive Web Traffic with Search Engine Optimization
Develop a Position on Cloud Platform as a Service
Vendor Landscape: Application Lifecycle Management
Vendor Landscape: Mobile Enterprise Application Platforms
2016 Applications and Information Management Trends
Develop a Fit-For-Purpose Modernization Process For Legacy Applications
Move to a Microservices Architecture to Reduce Maintenance Cycles
Make Sure Your First 100 Days in Applications Are Not Your Last