PPM and ALM Features

PPM - ALM Bridging the Development - Operations Gap

Simply!

 

It does not need to be complicated, or expensive.  We all know that the process from Project Initiation to Project Deployment and Configuration Management is generally in need of streamlining. 

 

In many organizations an attempt has been made to automate the process, but it is generally in segmented silos of work such as a tool for projects, a tool for development and a tool for release.  Or, a universal, all encompassing enterprise approach has been tried – but often failed.

 

So, what is the dilemma?  Generally each work unit along the way has its own sub-process, and may in fact need its own tools.  These tools are, or should be best in class for things like QA, testing, Code Management, Monitoring, etc.  But, these tools do not necessarily need to be embedded in an overall process and toolset that the greater business organization needs to govern the efficiency and effectiveness of the Project Initiation to Deployment Process. 

 

At CIO Services, LLC, we believe a different approach should be taken, and we have embodied the process in a tool we call PPM Litecycle TM.  Below is a diagram of the main application page, which also shows the elements of the process followed.  Yes, the deeper functionality an individual component may need to do their work may not be there, but the process should be envisioned as sitting above the lower level details.  However, the progress and needed approvals are tracked as the process moves along. 

 

One key point is the handoffs along the way.  For example, when a project feature has its necessary approvals, the feature moves from the project side of the application to the Release Management side, where it is handled by the Operations Team, or an intermediate Release Management Team.  And, before moving to Deployment, a change document is created, with all appropriate artifacts the CAB needs to know prior to approving the change.

 

There are process handoffs like this all along the process.  The end, and desired result, is an overall Project to Deployment governance process and workflow, which bridges the Development -  Operations Gap for a smooth, uncomplicated implementation.  And, last but not least, the process can present necessary artifacts to any auditor that may want to see the history of how an implementation took place.

 

 

 

 

Widening out PPM to include Services Management Features

Elements of ITIL and Cobit built in

PPM Litecycle TM

PPM—ALM—Governance—Workflow