Use actual accounting data on the performance of your last project to compare how accurate your estimates were versus the real thing. The Actual ROI tool is a quick way to show you how your project performed against the plan and identify areas for improving your estimating skills.
The Analytical Hierarchy Process (AHP) is a quantitative decision-making methodology that uses pair-wise comparisons to determine the importance of relative evaluation criteria and the relative strengths of decision alternatives. This document is a crash-course in AHP and is designed to help get you making difficult project decisions (particularly package software-related ones) quickly, confidentally and rationally.
Function points are a measure of the size of a software system. To convert function points into levels of effort, the productivity of the enterprise's development teams must be known or estimated. This three-for-one zipped deliverable includes a document explaining function point analysis, instructions on how to apply a function point analysis and a worksheet set up for an Albrecht function point analysis.
This template is for creating a process inventory and detailed process descriptions for the purpose of Business Analysis prior to IT project implementation. Processes are analyzed step by step in order to identify software functional requirements that are necessary to execute the process. A companion to the article The Role of Business Process Design in Business Analysis on IT Projects.
Planning a project necessitates analyzing your client's business and determining system requirements based on business structure. What business areas will be addressed, how do they translate to functionality, and how is that functionality prioritized? Start with an organizational mapping of business areas to functions, like this example from the insurance/finance industry.
This template is designed to assist in planning for project rollout. It helps identify operational impacts in a number of different areas, both for the rollout period and ongoing after the project has launched. It should be developed during project planning and revisited during project execution as needed.
What data should you keep in a Data Warehouse and why? This form helps you identify the needed data and its associated characteristics in relation to your business requirements.