A program is a group of related projects designed to accomplish a common

goal over an extended period of time.

Each project within a program has a project

manager. The major differences lie in scale and time span.

times where.

Example 1- as a result of extensive market research a computer software company decides to develop a program that automatically translates verbal sentences in English to Russian. The project should be completed within three years at a cost not to exceed $1.5 million.

Example 2 - To design and construct a portable hazardous-waste thermal treatment system in 13 months at a cost not to exceed $13 million.

Project Scope- The product scope answers the question “What end result is wanted?”

Example - if the product is a cell phone, its product scope will be its screen size, battery, processor, camera type, memory, and so on.

Justification - the business case for the project. Why did you authorize this project? it usually includes cost/benefit analysis and strategic significance.

Example - On a new release project, the justification may be an expected ROI of 30 percent and an enhanced reputation in the marketplace.

Deliverables - measurable outputs over the life of the project. Example - deliverables in the early design phase of a

project might be a list of specifications. In the second phase deliverables might be software coding and a technical manual. The next phase might be the prototype. The final phase might be final tests and approved software.

Milestones - milestone is a significant event in a project that occurs at a point in time. The milestone schedule is built using

the deliverables as a platform to identify major segments of work and an end date—for example, testing complete and finished by July 1 of the same year.

• Scrum

• RUP (Rational Unified Process)

• Extreme Programming (XP)

• Crystal Clear

• Agile Modeling

• Dynamic Systems Development Method (DSDM)

• Learn Development Rapid Product Development (RPD)

To find the critical path,

1. List down the activities

2. Identify dependencies

3. Create a network diagram

4. Estimate the duration for each activity

5. Find the critical path based on the longest sequesnce

The following eight rules apply in general when developing a project network:

1. Networks flow typically from left to right.

2. An activity cannot begin until all preceding connected activities have been completed.

3. Arrows on networks indicate precedence and flow. Arrows can cross over each other.

4. Each activity should have a unique identification number.

5. An activity identification number must be larger than that of any activities that precede it.

6. Looping is not allowed (in other words, recycling through a set of activities cannot take place).

7. Conditional statements are not allowed (that is, this type of statement should not appear: if successful, do something; if not, do nothing).

8. Experience suggests that when there are multiple starts, a common start node can be used to indicate a clear project beginning on the network. Similarly, a single project end node can be used to indicate a clear ending.