Most Ivanti Neurons for ITSM projects fall apart either during UAT or after go-live, for the same reason: Poorly planned and executed UAT! What about business and technical requirements? Well those are likely flawed too. How do I know that? After 28+ years of Ivanti Neurons for ITSM / ITAM implementations, nothing surprises me anymore. Especially poorly done business requirements. And quite frankly a lack of distinction of business requirements from technical requirements. Add a junior consultant (less than 20 years experience, less than 50 implementations) and your probability of scope creep and budget ballooning goes up, and your end user morale and management support goes down.
When documenting business requirements as well as technical requirements after business requirement sign-off, UAT Test Scrips should be front and center. Waiting until the system is configured is often too late. You see UAT Test Scripts go hand in hand with Use Cases, and if your Use Cases aren’t documented then you’re taking a huge gamble with your Ivanti Project success.
What can you do to ensure users get the system they need and testers are able to validate your business and technical requirements?
- Differentiate between Business Requirements (end users standard operating procedure) and Technical Requirements (user interface, configuration, coding, data exchange)
- Determine who owns what UAT Test Scripts. This is where your lead subject matter experts get involved.
- Write UAT Test Scripts based on your Use Cases, categorized by subject matter. Similar to writing a recipe for your favorite meal. Review as a team
- Avoid these common UAT pitfalls
- Trust the process
- Last but not least, follow the process. No short cuts.
ITSM/ITAM/ESM Blog 