1. create a work-breakdown structure (WBS is a hierarchy of the tasks required to complete a project) ; every task should culminate in one or more results called deliverables ex: documents, designs, prototypes, etc.
2. estimate time and costs- license packages, such as ERP systems, that include both business processes and information system components- the schedule risk of integration activities is far less than those for developing processes, programs, databases, and other components. You can however attempt to schedule the development project in spite of all of the difficulties- if you do computer coding it only schedules for software components.
3. create a project plan- list of WBS tasks, arranged to account for task dependencies, with durations and resources applied. Given dependencies, estimates for task duration and resource requirements are than applied to the WBS to form a project plan; Gant chart shows tasks, dates, and dependencies
4. adjust the plan via trade-offs- attempt to reduce time and costs. Trade off- a balancing of three critical factors: requirements, cost, and time
5. manage development challenges
4 factors to consider:
2. Diseconomies of scale
3. Configuration control- refers to a set of management policies, practices, and tools that developers use to maintain control over the project's resources such as documents, schedules, designs, program code, and any shared resource needed to complete the project
4. Unexpected events