Book Image

ServiceNow for Architects and Project Leaders

By : Roy Justus, David Zhao
Book Image

ServiceNow for Architects and Project Leaders

By: Roy Justus, David Zhao

Overview of this book

ServiceNow is the leading enterprise service management platform that enables the effective management of services in a modern enterprise. In this book, you’ll learn how to avoid pitfalls that can challenge value realization, where to focus, how to balance tradeoffs, and how to get buy-in for complex decisions. You’ll understand the key drivers of value in ServiceNow implementation and how to structure your program for successful delivery. Moving ahead, you’ll get practical guidance on the methods and considerations in securely using ServiceNow. You’ll also learn how to set up a multi-instance environment including best practices, patterns and alternatives in the use and maintenance of a multi-instance pipeline. Later chapters cover methods and approaches to design processes that deliver optimal ROI. Further, you’ll receive tips for designing technical standards, designing for scale, ensuring maintainability, and building a supportable instance. Finally, you’ll focus on the innovative possibilities that can be unlocked in a ServiceNow journey which will help you to manage uncertainty and claim the value of being an early adopter. By the end of this book, you’ll be prepared to lead or support a ServiceNow implementation with confidence that you’re bringing not only a solution but also making an impact in your organization.
Table of Contents (17 chapters)
Part 1 – Pursuit of Value
Part 2 – The Checklist
Part 3 – From Success to Innovation

Designing your ServiceNow landscape

Both the most and least useful thing you can learn about designing a ServiceNow landscape is that the correct design depends on many factors, including your team’s level of experience, the number of instances at your disposal, and the types of applications and configurations you’ll be building. Fortunately, we’ll look at more practical advice in this section, including the most common scenarios and principles you can use to inform your own design.

Two-instance landscapes

The easiest scenarios are when you have two or three instances with two instances being rare in all but the smallest deployments. In the case of two instances, you’ll use one production instance as production, and the remaining instance will act as both your development and testing instance:

Figure 6.4 – Two-instance landscape design (using update sets)

Customers using only two instances almost always use update sets...