I wrote a blog a while back on hazy requirements that I would like to expand on a bit today…

Whether you’re implementing DNN or another platform, you need requirements to build whatever it is you intend on building.  Requirements are the cornerstone for the project scope. These have to be clearly defined if you wish to be successful in the execution of your project. Otherwise, it’s easy to waste time and money developing incorrect or even unneeded functionality.

Requirements gathering is an important part of the early stages of a project. While sometimes requirements are fed through the RFP from a client, they often are vague and consist of some red flag phrases, such as “easy to use” or “cutting edge”, when referring to design or navigation. These are not easily measured concepts, nor are they real requirements. Sometimes you may come across “requirements” that seem more thought out, like “must integrate with existing systems and / or databases”. While from a high-level business sense this may seem like a requirement, it is virtually impossible for anyone to quote a cost for implementing a solution to integrate with anything without working knowledge of the API.

Clear requirements and scope also help the project manager keep the project on task and on budget. Part of AppTheory’s process is going through a discovery phase with the client at the beginning of each project to make sure our understanding of the requirements, business rules, and approach are in line with one another. This helps define the work to be done, confirms that it was estimated correctly and ultimately results in a Vision Scope document, which is then used to guide the project plan.

For more info on the AppTheory Solution Framework, view our pdf here.