Authors: Steven Ormston - ServiceNow Account Manager, Agnieszka Milecka - Marketing Manager
The goal of gathering requirements for ServiceNow project, or any other software development project, is to review:
The requirements constitute the area in between these 2, and specifies existing issues and/or areas for improvement. In the case of new projects and innovations, “the as is” will be a blank canvas.
The system should support people, processes and the very business. And your requirements should reflect these. Examples in the IT, can be Incident or Request Fulfillment; in HR, we can look to new hires, leaves etc.
1 of the issues is that requirements can sometimes be elusive. A stakeholder may want something, but isn’t able to define what it actually is or how it looks like. To succeed in their definition:
That’s the foundation.
An analyst can use various techniques and approaches to collect requirements:
Once the stakeholders have provided their input, it requires analysis and further validation to confirm it’s fully understood. At each stage, full understanding is the key to a successful project delivery. So ask questions until there is no doubt. These steps will help refine the deliverables for the project.
The collection of requirements is a cost, yet only provisionally. This cost allows you to optimize budget in the later stages of the ServiceNow project, turning into a saving tool. The analysis at the start of the project is most often less expensive than the replacement or repair of the issues arising if you don’t gather requirements beforehand.
Businesses often rush through this process. They don’t perceive it as a value added and almost never want to invest time and resources in the process before defining scope and setting up budget. The order should be different, starting from gathering requirements that allow to effectively manage both scope and budgets.
The aspects being subject to retrospective assessment of a ServiceNow (or any other) project are:
The requirements collection and definition process should be built into the project delivery plan. Plan for it carefully to make the most of this provisional cost and to turn it into a project gain. It’s as important stage for the delivery as the setup of budget, timeline and resources.
If you need any assistance in your ServiceNow project delivery, don’t hesitate.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.