- Large-scale projects are hard. In fact, so hard that 17% of failures of large projects are so bad they threaten the existence of the company.
- Enterprise applications have a multitude of stakeholders and can impact fundamental business processes.
- Failure to manage this complexity can have significant negative consequences.
Our Advice
Critical Insight
- Agility is not absolute. Being agile means using various techniques to get the right work done right. Sometimes that means traditional Waterfall techniques are the right answer.
- Look in all areas of the organization for usable skills. IT does not have a monopoly on the use of Agile. Be sure to look at all departments in the organization.
Impact and Result
- Leverage the Info-Tech methodology to find the process that fits your company while delivering the best chance to realize business value. Use one of the three methodologies, Waterfall, Agile, or custom, that best fits your organizational culture.
- Work with your vendor partner to ensure they are working in a compatible way with your selected methodology and tools.
- Find and leverage the skill sets you need from within your organization. Perhaps your marketing department is using Scrum or the help desk is using Kanban. These are capabilities you can leverage in the execution of your implementation.
Workshop: Choose a Best-Fit Enterprise Application Delivery Model
Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.
Module 1: Govern and Manage Revisited
The Purpose
- Set the stage by establishing a common language.
- Understand what your organization implementation strategies and gaps.
Key Benefits Achieved
- Organizational terms and definitions
- Organizational and Vendor implementation capabilities
- Capability gaps and remediation steps
Activities
Outputs
1.1
Set your starting point.
1.2
Prepare for the change.
Module 2: Tools, Tools, Tools
The Purpose
- Achieve a better understanding of success and failure through scenario planning.
- Identify the practices and tools that fit with your organization.
- Understand why you should reduce customization.
- Ensure the quality and importance of your data.
Key Benefits Achieved
- Success and failure scenarios to help understand the risks and how they can be mitigated
- A “toolbox” filled with practices that fit with your organizational capabilities
- Principles to follow to avoid expensive customizations with low return on investment
Activities
Outputs
2.1
“What if” the future.
- Success and failure scenarios and the assumptions made about the path.
2.2
Select your tools.
- Practices, tools, and project metrics
2.3
Processes and data.
- A set of principles to guide acceptance of customizations and list of activities such as conversions associated with data.
Module 3: Implementation
The Purpose
- Understand the need for organizational change management focusing on clear communication.
- Identify what is needed to proceed with a successful implementation.
Key Benefits Achieved
- An organizational communications plan to build acceptance
- A training plan to build comfort with the new software
- A checklist to ensure everything is prepared to transition to live
- A checklist to ensure the transition to live goes as smoothly as possible
Activities
Outputs
3.1
Manage the change.
- Plans for both organizational communications and training
3.2
Transition.
- A checklist for transition to live readiness and a checklist for the transition.