Web design software - 196 Part II: Planning Your Software Project your
196 Part II: Planning Your Software Project your stakeholders confidence in you. In order to create an accurate estimate, you need to include the following in every estimate you create: Product scope: The product scope documents the product requirements and the characteristics of the product (for example, a list of the software functionality). It includes thorough detail in order to facilitate further project planning. Project scope: The project scope describes the project deliverables and defines the work that will be accomplished. It includes product requirements, schedule milestones, WBS, assumptions and constraints, and methods of change control. It also defines the process for how the final deliverable will be accepted by the customer. Assumptions: You assume there won t be delays. You assume you ll have all the resources you need. You assume that this is an estimate, not a quote. Constraints: Any constraints that have been brought to the table at this point need to be documented. A constraint is anything that limits the project manager s options; examples can include Time constraints: You must have the project done in four months. Resource constraints: You can only use two developers on the project. Development environment restraints: You must develop in COBOL. Budget restraints: Your budget is capped at $250,000. Timeframe: We discuss timeframe in detail in Chapter 8. Essentially, you need to let stakeholders know that this estimate is a limited-time offer that depends on currently available resources. If the stakeholders want to do this project in five months when all your developers are wrapped up in other projects, you might have different numbers. Range of variance: The range of variance describes the +/ every estimate should have. For example, as discussed previously in this chapter, you create a ROM estimate for a project to create a new piece of software. You estimate the project to cost $150,000 with a possible variance from +25 percent to 10 percent. For input into the range of variance, you use any or all of the following resources: marketplace conditions, commercial databases, cost-estimating policies and templates, historical information, project files, team members knowledge, lessons learned documentation, project scope statement, WBS, project management plan, schedule management plan, resource management plan, and risk register.
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.