Python Notes for mca i year students osmania university.docx
Project Preparation and Management
1. Dr. P. P. Patel
Director of Extension
Education,
Directorate of Extension
Education
University Bhavan,
Anand Agricultural University,
ANAND-388110
Prepared by:
Dr. Arpita Sharma
Assistant Professor,
Directorate of Extension
Education
University Bhavan,
Anand Agricultural University,
ANAND-388110
2. A project refers to a specific undertaking or venture
that is to be carried out within an identified time frame.
Is a temporary endeavor designed to produce a unique
Product
Service
Result with a defined beginning
End undertaken to meet unique goals and objectives.
3. Are efforts to achieve objectives.
Have a start, a middle and an end.
Different from operational activities.
Core skills involved in project management including
identifying and agreeing on project objectives, scheduling and
estimating.
In addition other issues such as managing risk, communication
and dealing with other people are key areas of importance.
4. Objectives of any project should be:
S – Specific
M – Measurable
A – Agreed upon
R – Realistic
T – Time related
6. Project management is the discipline:
Projecting or planning,
Organizing,
Motivating and controlling resources
To achieve specific goals and meet specific
success criteria.
7. To explain the main tasks undertaken by project managers.
To introduce software project management and to describe its
distinctive characteristics.
To discuss project planning and the planning process.
To show how graphical schedule representations are used by
project management.
To discuss the notion of risks and the risk management
process.
8. 1. Initiate the project
2. Identify the Project Manager
3. Develop the Project Charter
4. Conduct a Feasibility Study
5. Define Planning Phase
6. Sign off on the Project Charter
9.
10. 1. Organize and staff the project.
2. Develop a Project Plan.
3. Sign off on the Project Plan.
11. Execute the Project Plan
Manage the Project Plan
Implement the project’s results
Sign off on project’s completion
12. Document the lessons learned during the project.
After-implementation review.
Provide performance feedback.
Close-out contracts.
Complete administrative close-out.
Deliver project completion report.
13. Proposal writing.
Project planning and scheduling.
Project costing.
Project monitoring and reviews.
Personnel selection and evaluation.
Report writing and presentations.
14.
15. Probably the most time-consuming project
management activity.
Continuous activity from initial concept through
to system delivery.
Plans must be regularly revised as new information
becomes available.
Various different types of plan may be developed to
support the main software project plan that is
concerned with schedule and budget.
16. Establish the project constraints.
Make initial assessments of the project parameters.
Define project milestones and deliverables.
While project has not been completed or cancelled loop
1. Draw up project schedule.
2. Initiate activities according to schedule.
3. Wait ( for a while )
4. Review project progress.
5. Revise estimates of project parameters.
6. Update the project schedule.
7. Re-negotiate project constraints.
17. The project plan sets out:
◦ The resources available to the project;
◦ The work breakdown;
◦ A schedule for the work.
18. Introduction.
Project organisation.
Risk analysis.
Hardware and software resource requirements.
Work breakdown.
Project schedule.
Monitoring and reporting mechanisms.
19. Split project into tasks and estimate time and resources
required to complete each task.
Organize tasks concurrently to make optimal
use of workforce.
Minimize task dependencies to avoid delays
caused by one task waiting for another to complete.
Dependent on project managers intuition and
experience.
20. Estimate resources
for activities
Identify activity
dependencies
Identify
activities
Allocate people
to activities
Software
requirements
Activity charts
and bar char ts
Create project
char ts
21. Graphical notations used to illustrate the project
schedule.
Show project breakdown into tasks.
Tasks should not be too small.
They should take about a week or two.
Activity charts show task dependencies and the the
critical path.
Bar charts show schedule against calendar time.
23. PERT – Performance Evaluation and Review
Technique
[1] Better for software-oriented projects.
[2] Uses 3 time estimates to determine most probable.
CPM – Critical Path Method
[1] Better for construction type projects.
[2] One time estimate.
24.
25. • The modern approach to project management may be
traced back to the middle of the 20th
Century when the US
Navy’s special Projects Office was formed in 1957 to
support the nuclear submarine project.
• The PERT method (program evaluation and review
technique) was established to analyse the tasks involved
in completing a complex project.
• Is the identification of the critical path, that minimum
amount of time that the project will consume given the
various activities involved and how they relate to each
other.
27. CPM was developed as a joint venture between DuPont
Corporation and Remington Rand Corporation for managing
plant maintenance projects.
Critical Path: Sequence of tasks that forms the longest
duration of the project
Float
◦ Amount of time that an activity may be delayed from its
earliest possible start date without delaying the project
finish date
◦ Latest possible finish date – earliest possible start – duration
= total float
29. PERT stands Program Evaluation and Review Technique.
CPM stands for Critical Path Method.
Is used to plan the scheduling of individual activities that make up a
project.
Can be used to determine the earliest/latest start and finish times for
each activity, the entire project completion time and the slack time
for each activity.
Are similar in their basic approach, they do differ in the way activity
times are estimated.
Three times (optimistic, pessimistic and most likely times) are
combined to determine the expected activity completion time and its
variance.
Thus, PERT is a probabilistic technique: it allows us to find the
probability of the entire project being completed by any given date.
CPM is called a deterministic approach.
It uses two time estimate, the normal time and the crash time, for
each activity..
32. Is a deliverable oriented grouping of the work involved in a
project that defines the total scope of the project.
Is a foundation document that provides the basis for planning
and managing project schedules, costs, resources, and
changes.
Decomposition is subdividing project deliverables into smaller
pieces.
33. Breaks large project into manageable units:
◦ Total project
◦ Subprojects
◦ Milestones
◦ Major activities
◦ Work packages
Helps to:
Identify all work needing to be done.
Logically organize work so that is can be scheduled.
Assign work to team members.
Identify resources needed.
Communicate what has to be done.
Organize work using milestones.
34. Guidelines: Some organizations, such as the DOD, provide
guidelines for preparing WBSs.
Analogy approach: Review WBSs of similar projects and
tailor to your project.
Top-down approach: Start with the largest items of the
project and break them down.
Bottom-up approach: Start with the specific tasks and roll
them up.
Mind-mapping approach: Write tasks in a non-linear,
branching format and then create the WBS structure.
35. The primary challenge of project management is to
achieve all of the project goals and objectives while
honoring the preconceived constraints.
The primary constraints are scope, time, quality and
budget.
The secondary and more ambitious challenge is to
optimize the allocation of necessary inputs and
integrate them to meet pre-defined objectives.
We can see in this slide how the three core issues of quality, cost and time fit together. This enables the focus to be determined in terms of maximising quality at the possible expense of increased cost and/or taking longer to complete the project, or minimising cost at the with the result of a possible reduction in quality and taking longer over the work or completing the project in minimum time incurring possible extra cost and reduction in quality.
At the same time the context of the project is shown taking into account organisational politics, personal objectives of those involved, business pressures, external pressures such as carbon footprint issues and stakeholder perceptions.
Study questions: Which of the three core issues of quality, cost and time tend to dominate in your organisation? What factors exist in your organisation which tend to make project working more difficult than perhaps it should be?
In this slide we see how one relatively simple project can be represented in a two dimensional graphical form. There are five milestones or states which must be reached. Milestone 1 is the starting point where resources have been assembled. Two activities then take place in parallel: activity A which is estimated to take 3 months leading to milestone 2 and activity B which is estimated to take 4 months leading to milestone 3. Milestone 2 is then followed by two activities D taking 1 month and E taking 2 months. D leads to milestone 4 which is then followed by activity F duration 3 months which leads to milestone 5. Milestone 3 is followed by activity C which leads directly to milestone 5. All activities are estimates in terms of duration and it can be seen that there is slack in activity E the start of which could be delayed by up to 2 months while D and F are underway and activity A which could be delayed by a month. This is an important point in terms of project planning for the use of resources and is an issue to which we will refer later.
Study questions: Can you now represent the process of making the cup of tea with the activities you identified in the previous slide as a PERT chart along the lines of that shown in this slide? Are there any resource and timing issues you can identify from your diagram?