I have been having a conversation about requirements with a colleague. I have addressed this in the past but it is worth revisiting.
A PLM implementation has 4 major components: Analysis, Design, Construction and Implementation. [This is true for most enterprise software projects.]
The output of the analysis generally includes a requirements document, a project plan and project scope. If these are done well, a programmer can easily create a design, construct a solution and implement it.
When the analysis is not thorough, the project will be subject to many changes as it is being worked. These changes will delay the project and usually makes it difficult.
When I am working on an analysis, I always start with the last, best list of details that I need to know. As I work with my client, I will be adding important details and likely removing some that are not relevant to their business. Working through an analysis will provide some great insights into that company. That knowledge leads to a better requirements document which in turn will yield a better project plan and scope definition. Do your best to avoid scope creep – it is hard to hit a moving target.
I believe that the user interface is an extremely important part of the requirements document, so I spend a lot of time working through what it should look like. The easier it is for the user to use the solution, the better the solution. If the programmer knows what the user interface should look like and how it should function, their job will be much easier.
Done right, the analysis component often takes at least ½ of the project time.
Done right, the finished solution should meet your expectations and everyone wins.
Contact me if you would like some help…