Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Monitoring and Control in Software Project Management, Exams of Computer Science

The importance of monitoring and controlling a software project to ensure its progress and meet targets. It covers topics such as creating a framework, responsibility, setting checkpoints, collecting data, cost monitoring, baseline budgets, earned value analysis, prioritizing monitoring, getting project back to target, and managing contracts. The document also includes visual aids such as slip charts, ball charts, and cumulative cost charts.

Typology: Exams

2022/2023

Available from 07/13/2023

yerisamson
yerisamson ๐Ÿ‡บ๐Ÿ‡ธ

41 documents

1 / 50

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Unit โ€“ IV Presentation
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32

Partial preview of the text

Download Monitoring and Control in Software Project Management and more Exams Computer Science in PDF only on Docsity!

Unit โ€“ IV Presentation

Unit โ€“ 4 (Monitoring and Control)

1) Creating Framework

๏ƒ˜ (^) Exercising control over a project and ensuring that targets are met is a matter of regular monitoring. ๏ƒ˜ (^) Finding out what is happening and comparing it with current targets. ๏ƒ˜ (^) The projects starts its execution, the project must be carefully monitored to ensure the projectโ€™s progress. ๏ƒ˜ (^) Expected outcomes are compared with the actual ones.

๏ƒ˜ (^) Standard oral communication of minutes are kept where as written type gets the reporting issues in a separate written format. ๏ƒ˜ (^) Formal ad hoc are mostly received information of different levels towards the end of the project and generate written reports. ๏ƒ˜ (^) Informal, oral and ad hoc provides early warning to the system and must be backed up by formal reporting procedures.

๏ƒ˜ (^) Single activity will not yield a deliverable work product but a group of activities can achieve the specified tangible product. ๏ƒ˜ (^) The development of the project measures the progress assessment. ๏ƒ˜ (^) It is carried out by the team members who are associated with the project activities. 1.3) Setting checkpoints ๏ƒ˜ (^) Regular ๏ƒ˜ (^) Tied to specific events such as the production of a report.

1.4) Taking snapshots ๏ƒ˜ (^) Manager needs to receive information about progress will depend upon the size and degree of risk of the project. ๏ƒ˜ (^) Progress reviews will generally take place at particular points during the life of a project it is known as review points or control points.

2) Collecting the data

๏ƒ˜ (^) Gather information about partially completed activities. ๏ƒ˜ (^) Difficult to make the forecasts accurately.

Traffic-light methods, ๏ƒ˜ (^) Green โ€“ on target ๏ƒ˜ (^) Amber โ€“ not on target but recoverable ๏ƒ˜ (^) Red โ€“ not on target and difficult to recover ๏ƒ˜ (^) Review all second level elements to reach the first level assessments. ๏ƒ˜ (^) Review both first and the second level assessments to produce an overall assessments. ๏ƒ˜ (^) Focus on non achievement factors. ๏ƒ˜ (^) Assessment forms can be used to evaluate the overall status of the project. ๏ƒ˜ (^) Critical activities denoted by red color.

3) Visualizing progress

๏ƒ˜ (^) A manager needs some way of presenting that data to greatest effect. ๏ƒ˜ (^) Some methods of presenting picture are, ๏ƒ˜ (^) Gantt chart โ€“ tracking project progress ๏ƒ˜ (^) It is the simple and the oldest form of representing the progress of the project. ๏ƒ˜ (^) It consists of activity bar that indicates the scheduled activity dates and the duration along with the activity floats.

๏ƒ˜ (^) Slip chart โ€“ visual indication of activities that are not progressing to schedule. ๏ƒ˜ (^) An alternative view of Gantt chart by providing a visual indication of those activities which are not on schedule. ๏ƒ˜ (^) The more bend in the greater the variation in the project plan. ๏ƒ˜ (^) If the slip line deviates more towards the non achievement of project objectives then it has to be reconsidered ๏ƒ˜ (^) Additional slip lines can be included at regular intervals.

๏ƒ˜ (^) Ball charts โ€“ way of showing or not targets have been met or not. ๏ƒ˜ (^) It is represented in the form of circles that indicate the start and the end point completion of activities. ๏ƒ˜ (^) Circles of the ball chart mostly contain only two dates the original and the revised one. ๏ƒ˜ (^) An activity is denoted by a red circle and green color denotes that the activity is ahead of its schedule. ๏ƒ˜ (^) Slippage in the project completion date but it is overcome by the timeline charts.

๏ƒ˜ (^) The Timeline โ€“ recording and displaying the way in which targets have changed. ๏ƒ˜ (^) The chart represents the planned time along the horizontal axis and the actual time along the vertical axis. ๏ƒ˜ (^) A line down the horizontal axis represents the scheduled activity completion dates and the slip in the line indicates a delay in the respective activities. ๏ƒ˜ (^) It is used to calculate the duration of execution of the project.