Building maturity

Most large companies and organizations commonly have issues around adoption of new tools, these include:

Vendor management (contract, licensing, support)
Staff turnover (new staff joining and SME's (Subject Matter Expert) leaving)
Lack of supporting process (documentation required to support a process within the tool)
Disparate working environments & teams (lack of communication)

Some of these can be addressed by having COP sessions (Communities of Practice) with reps from all the relevant teams to discuss strategy, process or "Best Practice" and how to's.

This is also a great forum to engage users and build the foundation for improved communication between the "Service provider" and customer.

Most issues are usually resolved over time assuming the organizational structure has not dramatically changed in the meantime.

SDLC Lifecycle Overview

1 Planning: Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.

2 Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

3 Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudo code and other documentation.

4 Implementation (Development): Code, test, install, and support the information system.
— Acceptance, installation, deployment The final stage of initial development, where the software is put into production and runs actual business.
— Integration and testing Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.

5 Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more.