Use cases | digipmo

Some use cases
All templates mentioned below are available in all digipmo configurations, and can be customized or cumulated (different projects can use different templates).
Some other templates not listed here are also available. Should you have specific needs or questions, please tell us which one using the contact form at the bottom of this page.

SAP projects features

SAP projects are typically large projects, involving teams located on several phyiscal sites (business teams, IT and consulting teams, off-shore development team, etc), often in several countries
It concerns several functional domains, with interdependencies
They rely on waterfall methodology with some specific activities (e.g. fit/gap workshops, transport orders, cut-over, etc) and some important milestones (e.g. end of Design phase, where coverage of business needs must be formally confirmed, before the Build of solution is started)
There are several test cycles (often called Unit tests, Integration tests, Simulation tests) generating an important volume of issues, causing back and forth between business, functional IT and development teams

How does digipmo help you?

Pre-configured project methodology for SAP Core Model Design & deployment
Pre-configured workflows for SAP Design workshops, SAP Customizing, RICEFWs, Training Component, Training session, etc
Issues are logged at object level (process, customizing, development, etc) with ‘in-context’ collaboration between teams
Functional and technical documentation sharing, with automated versions history
Progress, issues and delays reported by team, by company, by geography, etc
Automated preparation of Weekly status meeting support and Steering Committee meeting presentation

Process Reengineering projects features

Process Reengineering projects vary in ambition, size and duration
In the recent years, Process Reengineering tend to follow an Agile methodology, except for really complex projects with deep impacts in several major IT systems at the same time
Reviewed processes are grouped by function or sub-function to optimize the mobilization of business resources and the identification of interdependencies
Solution is defined via interviews, workshops, impact analysis and then implemented (IT and change management)
The project success is measured with KPIs, defined at project start (calculation methods, baseline and target values), and measured along the project execution

How does digipmo help you?

Pre-configured project methodology for Process Reengineering
Pre-configured workflows for Process Design workshops, IT impact, KPI, Change Management, Training Component, Training session, etc
Functional and technical documentation sharing, with automated versions history
Progress, issues and delays reported by process, team, geography, etc
Automated preparation of Weekly status meeting support and Steering Committee meeting presentation

Post-Merger Integration projects features

Post-Merger Integration can be considered as a Program, combining a large number of Projects with impacts in different functional domains
A part of these projects are mostly related to IT (extension of an existing application to new users, licenses acquisition, data migration, change management and training)
Some projects are mostly a change in processes (Treasury, HR & Payroll, etc), especially for the acquired company or business
A PMI program contains a major ERP component, with impacts on processes, customization and interfaces
During or after a PMI Program, Value Realization initiatives are conducted to maximize the benefits of the merger on profitability, business performance and process efficiency

How does digipmo help you?

Pre-configured project methodology for Post-Merger impact assessment, for Payroll implementation, for IT Application merge, for Process reengineering, for Value Realization, etc
Pre-configured workflows for Data migration, Training Component, Training session, Change management, etc
Multi-dimensional Status reporting and progress reporting across organization
Real-time issue escalation and resolution process, with dedicated dashboards (by business unit, function, geography, etc)
Integrated Risk Management and Risk Matrix
Automated preparation of Weekly status meeting support and Steering Committee meeting presentation

Digital projects features

Digital projects usually involve business teams from 1 or 2 main functions (e.g. Sales, Finance, Logistics, etc), an IT team, and often an IT/Digital external partner
Digital projects are now almost exclusively delivered in Agile
Some early key success factors lie within the technological choices made upon project start (development framework, add-ons, connectors) and in the relevance of functions listed by business teams
They require a continuous collaboration between business and development teams, an efficient process to balance development priorities along the project and to control project budget evolution, and a multi-devices testing

How does digipmo help you?

Pre-configured project methodology for Digital projects
Pre-configured workflows for Design workshop, Agile development, Connector development, Training Component, Training session, etc
Development planning and development backlog management
Shared functional and technical documentation, with automated versions history
Issue management
Automated preparation of Weekly status meeting support and Steering Committee meeting presentation

Custom projects features

Some projects are ‘one-of-a kind’, with an ad hoc project approach, and little possible re-use or capitalization from previous projects
They require an initial effort from Project Management to define the project methodology, list of deliverables, roles and responsibilities, etc

How does digipmo help you?

Among various options offered to you in digipmo, you may choose depending on your context:

To apply the generic PMI© project methodology available in digipmo, whose 5 phases and 18 sub-phases suit most project types (some details here)
Or define your own specific project methodology, by defining in digipmo your own work breakdown structure and your own workflows