ServiceNow Implementation Methodology - StartNow

[dale_brown]

Want to learn more about the new implementation methodology from ServiceNow Professional Services?

Over the coming days / weeks / months, I'd like to share my thoughts and views around this methodology and how this came about in the first place. I'd also like to explain how this methodology is made up, what components of ServiceNow support the methodology and our future plans for it. I'd also like to get feedback from the field to see if we're on the right tracks!

First of all, what does it stand for, where did 'Start' in StartNow come from? The name was the basis for the whole ground up re-write…it stands for STrategic Alignment and Rapid Transformation. This really drove our thinking and set the tone for the development.

I'd like to explain really early on here that StartNow is a combination of traditional 'waterfall' approach and use of Agile Scrum with the inclusion of a central area to store project risk, so 3 main components are core to the methodology:

1.Project - Waterfall
2.Scrum — Agile
3.Risk

Why mix up Project management and Agile scrum? Basically we're utilizing the good bits from both methodologies! It's not one or the other; it's a combination of both! Maybe we should call it a 'Wagile' methodology!!! 🐵

Project Management — This is great for planning out your stall, its great at defining scope, deciding on the optimum strategy for delivery, creating teams as it's a methodical task oriented approach. Is still about delivering optimum value based on a predefined framework of time, cost and output and managing changes within this structure. The downside to this and I use a boat analogy; think of a steam-liner, once you start this on it's course, it's off and running but you really struggle to change it's course.

Agile scrum — This is at the end of the day a product development framework, its useful for delivering work in an iterative and incremental way. Requirements and solutions evolve through collaboration and each package of work is time-boxed (sprints). With this approach we can keep on-track with the customer requirements, drop in new requirements or remove anything that's deemed no longer required…we're now driving a speed-boat and can spin it around in a second!

Next in this series I'll explain in more detail what this means from a ServiceNow deployment perspective