ITSM: Application Portfolio - Create and Operationalize

0 %

Status

Project is 0 % complete, starting on Mon 4/20/20 and ending on Fri 6/16/23.

On Hold [On Hold]

0% complete, updated on Thu 6/2/22 10:23 AM by Greg Van De Mark

Changed On Hold Until from Fri 5/28/21 to Fri 12/30/22.
Update to the previous comment (last line changed)...
This project (processes and tools) was deemed too unwieldy to be handled as one project. There is another project (Software: Software Catalog) that is looking at how we can meet System requirements where we supply them lists of hardware and software. Once that project is complete, we'll take a look at this project again (and see if we can use outcomes of the other project). On hold for until the end of the calendar year as the other project is only 40% complete at this point.

Details

Dates
Mon 4/20/20 - Fri 6/16/23
Acct/Dept
Technology Services
Service
Projects and Changes / Project
Type
Projects and Changes / Consulting
Health
On Hold
On Hold Until
Fri 12/30/22
Classification
Project
Created
Fri 4/17/20 3:23 PM
Modified
Thu 6/2/22 10:23 AM

Description

AKA, Application Catalog, Application Management, Service Portfolio Management.
Create a process where we determine if a service should be onboarded, onboard it, maintain it, and retire it. Take advantage of repeatable tasks (checklists). Make visible to customers.

Risks

  1. Low Impact on Other Projects

    Most of our critical paths in other projects should not be on the critical path for this one. Steven's time can impact the success of his projects but he is regulating the number of projects he has active at one time in order to reduce this risk.

  2. High Lack of Commitment / Adoption

    DoTS culture runs counter to this initiative. Buy-in from the CIO is crucial. Communication of upcoming changes to applications early on will be quite different for some.

  3. Low Ongoing Support

    The team supporting this initiative is the one supporting it operationally.

  4. Low Unknown Complexity / Learning Curve

    Other organizations have application portfolios so this is not an unknown. Also, the process itself should not be complex.

  5. Low Vendor Dependence

    This is more of an unknown. A tool has not been identified. TeamDynamix may have this as a module. However, no matter the tool, the process will not be at risk. It can be done on paper if needed.

Systems Affected

  1. Applications - eSIS

    All applications.

  2. Applications - Hosted

    All applications.

  3. Applications - Not Hosted

    All applications.

Alternate Manager(s)

Sponsor

Stakeholders (2)

Joseph Kmiech
Joseph Kmiech
Consulted, Informed
CIO buy-in. Manager of managers.
Fri 4/17/20 3:11 PM
Peter Reese
Peter Reese
Informed
Supervisor.
Fri 8/14/20 8:19 AM