
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
I am taking inspiration from Kelly Kaufmann and attempting to present my firsthand account of our ServiceNow PPM implementation as we move along the maturation of our ServiceNow platform. For anyone who has not read her blogs, please search for Kelly's name and enjoy!
I am currently working for a rehab hospital as a one person PMO. I joined the team a little over a year ago after the IT senior staff had committed to approaching projects in a more formal process. Before I joined the team, our org had implemented ServiceNow ITSM. The key focus was on incidents, our service catalog, change management, and IT tickets. We continue to grow our use of ServiceNow and are leveraging the platform to improve our services and responses to our stakeholders. One pet-peeve for me is that I don't like to refer to our customers as "end-users," IT and drug dealers are the only people who refer to their customers as "users." I prefer stakeholders!
As a planner, yes, I am a planner to a fault. My adaptive organization traits are in the 99%! We will not talk about my natural tendencies. I am from southern Georgia (USA) and as the songs say, "I'm like a blue tick hound and like to lay around in the shade."
So back to planning, as I stated, before my arrival, our IT leadership team had don't a fantastic job creating a spreadsheet where we were keeping track of our ideas and demand. The spreadsheet was our first attempt at organizing around a demand of IS project. Since IS had already implemented ServiceNow and had identified PPM as our future project planning platform, the idea and demand process was built to match SN PPM.
We also defined a multi-phased approach to our PMO work following our crawl, walk, walk a little faster, and then running approach.
Oh, one more thing, as we are progressing in our PMO/ SN PPM efforts, our organization is implementing an enterprise-wide solution that we are treating as a separate program. They have their program director, and the program director is part of our IT leadership team, so the communications line stay open.
Our first objective for our PMO / PPM effort was to create a SharePoint site which we have used as our crawling and walking home base. For those readers use to SharePoint, we created a few simple lists for projects, programs, and a document library. The IS PMO SharePoint site has allowed us to easily keep track of our ideas, demands, and our project tracking. Since I created the site, I like it! We also created a project workbook for capturing our project milestones and RAAID. We have a few teams that are working with Agile, so we have both a Waterfall and Agile workbook.
Our key objectives for our work with the PMO are:
1) Simplicity
2) Make the project leadership process fun. It's fun to me, but not sure all our project leads would call it fun.
3) Listen to our teams.
4) Focus on the value of working together, developing people, and exceeding industry benchmarks.
For reference:
Initial implementation partner - Sovereign
ServiceNow Version - Kingston - Moving to London
ServiceNow Modules - ITSM, PPM will be our first ITBM module
Industry - Healthcare - Rehab hospital
Stakeholders - 2,000
Facilities - 3
IT Shop - 45
Service Desk - 4
I have attached several documents for sharing on our current toolset…
1) PMO Presentation
2) Project Workbook - Waterfall
3) Project Workbook - Agile
So this is our current state, I can't wait to do all the mapping to our future state in PPM! There is a ton of other background information. However, the key is that we are now moving in the direction of implementing SN PPM in 2019.
- 1,920 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.