Class on Thusrday, 2 August 2007

Chapter 3: Planning and Managing the Project

In this chapter, we will look at:

• Tracking Progress


• Project porsonnel and organization


• Effort and schedule estimation


• Risk management


• Using process modeling with project planning

I'll explain more in Tracking Progress.

Tracking Progress

A typical projects begins when a client approaches the developers to discuss a perceived need. This is during the Requirements Analysis phase in any software process models. This phase will lead to a design phase because design phase depends on the needs of certain customer. To meets with their requirements, a well-thought-out Project Schedule will be needed.

A Project Schedule is to describes the software-development cycle for a particular project by enumerating the phases or stages of the project and breaking each into discrete tasks or activities to be done. It also potrays the interactions among the activities and estimates the times that each activity will take.

To determine the project schedule, we will begin by working with customers and potential users to understand what they want and need. At the same time, we make sure that they are comfortable with our knowledge of their needs. During project development, the customer also take part of it. They will expects to see the deliverables which is the documents, demonstration of function, demonstrations of subsystems, demonstration of accuracy and the demonstration of reliability,security or performance of the project. To produce this deliverables, the developers must determine milestones and what the activities, what must happend and which activities depend on other activities,products or resources. A milestone is the completion of an activity - a particular point in time.

Project development can be separated into a succession of phases which are composed of steps, and each step can be subdived further into activities if necessary. Below is the graph of the project schedule.