GETSCOPE

For a project manager or business systems analyst, it’s customary to meet with a project to obtain project requirements signoff. However, what invariably happens is the customer deciding they need a new set of features outside the scope of the current requirements document. This dilemma, known as “scope creep” or “feature creep” is a common project killer, and it is critical for a project manager to know how to effectively manage this situation when it occurs. To easily identify scope creep, you first need to have a really good handle on what the requirements are. Make sure you have an organized requirements management document that includes a mission statement, a background statement that includes needs, the high level features, and as many detailed requirements as possible which all map back up to the features. By producing a rich and thorough set of requirements, you can get a clean baseline of what the system needs to do which can often mitigate any upfront scope creep.

Aero gives you the tools you need to take your firm’s knowledge capital and put it to work. Your processes and procedures are integrated with your tasks, making your firm efficient, scalable and profitable. With Aero, you’re confident that client work won’t slip through the cracks. One-time projects, recurring tasks, client emergencies — even email – are all seamlessly integrated into one list, so you and your staff have a clear view of what needs to get done today. With Aero, you have a clear overview of all client work: what’s done, what’s in progress and what’s about to be overdue. Aero’s integrated time tracking allows you to spot scope creep while it’s happening. Aero’s management reports help you to manage your practice with insights into metrics like staff performance and project job costing.