Why Build and Modify stages in the Service Factory Workflow requires effective Agile project management
I’ve got good news and bad news. Which one do you want to hear first?
First, let me tell you the good news. ServiceNow is a modern Software-as-a-Service (SaaS) style solution that is very flexible, easily configurable, and fast to build and modify. From ideation to functional definition to initial capability to building and modifying, ServiceNow is much faster than the tools and solutions of the past. You’d do well by taking full advantage of what ServiceNow has to offer.
Now to the bad news. Building and modifying today’s solutions, like ServiceNow, requires that you move at the speed of innovation, while lowering the risk of poor outcomes. Why is this bad news? Because older style implementation methodologies like Waterfall are too monolithic and slow to respond to growing and evolving demands; what’s required is the Agile development approach. The bad news isn’t that we MUST adopt a new development process, it is that most IT operations organizations don’t know WHERE to start.
To that end I’ll offer some insights in this article. But before I go into that, and in case you missed it from my recent blog posts, there are four stages in the services factory workflow: Consider, Build, Modify and Retire.