/
Software Engineering Week 4 – Planning & Managing Projects  #1 Software Engineering Week 4 – Planning & Managing Projects  #1

Software Engineering Week 4 – Planning & Managing Projects #1 - PowerPoint Presentation

accouther
accouther . @accouther
Follow
342 views
Uploaded On 2020-07-01

Software Engineering Week 4 – Planning & Managing Projects #1 - PPT Presentation

AA Gde Bagus Ariana ST gungarianayahoocom httpgungarianawordpresscom Management activities Project planning Project scheduling Critical Path Method CPM Program Evaluation and Review Technique PERT ID: 791250

activity project task time project activity time task amp management schedule path critical scheduling pert tasks method yang evaluation

Share:

Link:

Embed:

Download Presentation from below link

Download The PPT/PDF document "Software Engineering Week 4 – Planning..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Software

Engineering

Week 4 – Planning & Managing Projects #1

A.A. Gde Bagus Ariana, S.T.gungariana@yahoo.comhttp://gungariana.wordpress.com

Slide2

Management activitiesProject planningProject scheduling

Critical Path Method (CPM)Program Evaluation and Review Technique (PERT)

Content

Slide3

Ensuring that software is delivered on time and on scheduleSoftware development is always subject to

budget and schedule constraintsWHY???Software project

management

Slide4

Proposal writing.Project planning and scheduling.

Project costing.Project monitoring and reviews.Personnel selection and evaluation.Report writing and presentations.

Management Activities

Slide5

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.

Project planning

Slide6

Types of project plan

Quality PlanDescribes the quality procedures and standards that will be used in a project.

Validation Plan

Describes the approach, resources and schedule used for system validation.Configuration Management PlanDescribes the configuration management procedures and structures to be used.Maintenance PlanPredicts the maintenance requirements of the system, maintenance costs and effort required. Staff Development PlanDescribes how the skills and experience of the project team members will be developed.

Slide7

Slide8

Project plan structure

Slide9

Activity organization

Activities in a project should be organised to produce tangible outputs for management to judge progress.Milestones are the end-point of a process activity.Deliverables

are project results delivered to customers.The waterfall process allows for the straightforward definition of progress milestones.

Slide10

Activities and Milestones

Slide11

Project scheduling

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.

Slide12

The project scheduling process

Slide13

Work Breakdown

Slide14

14

Anatomy of a Project

PROJECT

PHASE 1ACTIVITY 1.1ACTIVITY 1.2ACTIVITY 1.3:PHASE 2PHASE nSTEP 1STEP 2:

STEP 1

STEP 2:

STEP 1

STEP 2

:

ACTIVITY 2.1

ACTIVITY 2.2

ACTIVITY 3.3

:

Slide15

Anatomy of a Project

Slide16

Scheduling problems

Estimating the difficulty of problems and hence the cost of developing a solution is hard.Productivity is not proportional to the number of people working on a task.

Adding people to a late project makes it later because of communication overheads.

The unexpected always happens. Always allow contingency in planning.

Slide17

Bar charts and activity networks

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

critical path.Bar charts show schedule against calendar time.

Slide18

Task durations and dependencies

Slide19

Activity network

Slide20

Activity timeline

Slide21

Staff allocation

Slide22

Have to consider workforce

RoleAbilityExperience etc…

Task not performed by the same personDependent on:

Project sizeStaff expertise & experienceDecide roles  decide type of peopleProject Personnel

Slide23

Extrovert

 tells others his thoughtsIntrovert

 asks others for suggestionsIntuitive

 base decisions on feelings & emotionsRational  examine facts & carefully considering all optionsWork Styles

Slide24

Rational extroverts

Assert their ideasNot let “gut feeling” affect their decisionBased on logic & not emotions

Rational introvertsAvoid emotional decisions

Willing to consider all possible courses of actionWork Styles

Slide25

Intuitive extroverts

Based on emotional reactionWant to tell others about themNo asking of inputIntuitive introverts

CreativeApplies it after lengthy analysis & findings

Work Styles

Slide26

Intuitive Introvert

Intuitive ExtrovertAsks Others Tell OthersAcknowledge feelings Acknowledge feelings

Rational Introvert

Rational ExtrovertAsks Others Tells OthersDecides logically Decides logicallyRATIONALINTUITIVEEXTROVERTINTROVERTProject Personnel

Slide27

Critical Path Method (CPM)

Slide28

Critical Path Method

Analysing paths among milestonesFind out minimum completion timeOutlines critical activitiesAllows estimation of real time/actual timeestimated amount of time required for the activity to be completed.

Allows identification of available timeamount of time available in the schedule for the activity’s completion

Deterministic method that uses a fixed time estimate for each activity

Slide29

Program Evaluation and Review Technique (PERT)

Slide30

PERT

Program Evaluation and Review Technique (PERT) network model that allows for randomness in activity completion timesNetwork of boxes (activities) & arrows (dependencies)Boxes can be used as

milestonesCritical path  similar meaning to CPM

Slide31

TugasMembuat Resume

ttg CPM dan PERT, tulis tangan di kertas double folio,

bahasa indonesia yang baik dan

benar.Untuk mahasiswa yang mengambil RPL hari Senin, berikut adalah referensi untuk tugas:http://www.youtube.com/watch?v=DdDzybQ_9vMReferensi lain yang berbahasa indonesia yang relevan. Buat tugas dengan sebaik-baiknya.Kumpul : 15 Oktober 2012, tidak ada toleransi keterlambatan. (jika tidak bisa hadir karena sakit/ijin, titip kepada teman)