Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

201 > Project Management > Flashcards

Project Management Flashcards

1
Q

Project Management

A

Organising, planning and scheduling software projects.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Software Management Distinctions

A
  • Product is intangible (cannot be seen or touched)
  • Software engineering is not recognised an an engineering discipline with same status as mechanical etc
  • Software development process is not standardised
  • Many software projects are one off projects.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Project Management Activies

A
  • proposal writing
  • project planning and scheduling
  • project costing
  • project monitoring and reviews
  • personnel selection and evaluation
  • report writing and presentations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Management Commonalities

A
  • these activities are not peculiar to software management
  • many techniques of engineering project management are equally applicable to software project management
  • complex engineering systems tends to suffer from the same problems as software systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project Staffing

A

May not be possible to appoint the ideal people to work on a project due to budget.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Project Planning

A

Most time consuming project management activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Types of Project Plans

A
  • quality plan
  • validation plan
  • configuration management plan
  • maintenance plan
  • staff development plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Quality Plan

A

Describes the quality procedures and standards that will be used in the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Validation Plan

A

Describes the approach, resources and schedule used for the system validation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Configuration Management Plan

A

Describes the configuration management procedures and structures to be used.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Maintanence Plan

A

Predicts the maintenance requirements of the system, maintenance costs and effort required.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Staff Development Plan

A

Describes how the skills and experience of the project team members will be developed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Project Plan Structure

A
  • introduction
  • project organisation
  • risk analysis
  • hardware and software resource requirements
  • work breakdown
  • project schedule
  • monitoring and reporting mechanisms
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Activity Organisation

A

Activities in a project should be organised to produce tangible outputs for management to judge progress.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Milestones

A

End-point of process activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Deliverables

A

Project results delivered to customers.

17
Q

Project Scheduling

A

Split project into tasks and estimate time and resources required to complete tasks.
Organise tasks concurrently to make optimal use of workforce.
Minimise task dependencies to avoid delays by one task on another task.

18
Q

Scheduling Problems

A

Estimating the difficulty of problems and hence the cost of developing a solution is hard.
Productivity != number of people working on task.
Adding people late can make it even later due to communication overheads.
Always allow for contingency in planning.

19
Q

Bar Charts and Activity Networks

A

Graphical notation used to illustrate the project schedule.
Activity charts show dependencies and the critical path.
Bar charts show schedule against calendar time.
Tasks should not be too small and should take a week or two.

20
Q

Risk Management

A

Concerned with identifying risks and drawing up plans to minimise the effect of those risks on the project.

21
Q

Product Risks

A

Affect quality or performance of the software being developed.

22
Q

Business Risks

A

Affect the organisation developing or procuring the software.

23
Q

Pert Charts

A

Project management tool used to schedule, organize and coordinate tasks within a project.
Includes time frames for tasks, like early start and late end.

24
Q

Risk Management Process

A
  • risk identification
  • risk analysis
  • risk planning
  • risk monitoring
25
Q

Risk Identification

A

Identify project, product and business risks

26
Q

Risk Analysis

A

Access the likelihood and consequences of these risks.

27
Q

Risk Planning

A

Draw up plans to avoid or minimise the effects of the risk

28
Q

Risk Monitoring

A

Monitor the risks throughout the project.

29
Q

Risk Types

A
  • technology
  • people
  • organisational
  • tools
  • requirements
  • estimation
30
Q

Risk Analysis

A

Assess probability and seriousness of each risk.
Probability may be very low, low, moderate, high or very high.
Risk effects might be catastrophic, serious, tolerable or insignificant.

31
Q

Risk Planning

A
  • avoidance strategies
  • minimisation strategies
  • contingency plan
32
Q

Avoidance strategies

A

Probability that the risk will arise is reduced.

33
Q

Minimisation strategies

A

The impact of the risk on the project or product will be reduced.

34
Q

Contingency plans

A

If the risk arises, contingency plans are plans to deal with that risk.

201 (16 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions