Ten Mistakes to Avoid When Gathering Requirements

Over the years our company has had a great deal of success helping customers retire and replace legacy monitoring platforms in favor of cheaper, faster and easier to manage systems. However, you don't simply fall out of bed and replace your Netcool Impact system with NOC HERO™ or SevOne with Zabbix. There is planning and preparation that goes into making this happen. That planning starts with gathering requirements to make sure your stakeholders are getting what they want and the system meets the needs of the business.

You may be thinking, "but we are migrating, it's like for like. We just need to ensure functionality is there in the new system and test it out." Wrong. Nothing could be further from the truth. Requirements gathering for a migration to a new platform is more important than in a greenfield. In a greenfield, expectations are there, but there isn't any basis for comparison. In a migration, your user community has things they like and things they don't like in the current system. However, this has to be balanced against the needs o