IT project teams are frequently asked by project sponsors / directors to scope a new piece of work; being a brand new project, increasing the scope or adding a new module to the existing system or replacing a legacy system. There are often a lot of unknowns and ambiguities, making scoping and estimation less than a straightforward task. More often than not the project team makes a few assumptions about the modules, tasks and steps required but it always comes down to the “effort” or “cost” which is in fact the most difficult part of the estimation, and in most cases this part is what the project sponsor is interested in the most!
Best practices and experience from other projects with similar scope and specification would make this process much more streamlined and more importantly makes the estimation more accurate.
See ArciFrame to learn more.