Project Planning Flashcards

(35 cards)

1
Q

Does good management guarantee success in a project?

A

No, but bad management nearly guarantees failure.

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

What are three common consequences of poor management?

A

Late deliverables, cost overruns, requirements failures.

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

Why does every project need a champion?

A

To advocate and fight for the project’s success.

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

Why is software management harder than managing physical projects?

A

Software is intangible, progress is difficult to see, and standard processes do not always apply.

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

Why is measuring “80% finished” in software misleading?

A

Because software projects often have evolving requirements and no clear completion point.

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

How do technology changes impact software project management?

A

Prior experience may become obsolete due to rapid technology evolution.

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

Name four key activities in software project management.

A

Requirements writing, planning & scheduling, costing, and monitoring.

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

Give three examples of deliverables in software projects.

A

Documents, completed software components, received hardware.

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

What does a software development plan include?

A

Development timeline, foreseeable risks, software components, dependencies.

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

What are three aspects of a quality plan?

A

Readability, maintainability, efficiency

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

What are three types of software maintenance?

A

Bug fixes, feature improvements, adaptation to new environments.

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

What is configuration management?

A

Managing different software versions, e.g., OS editions, pricing schemes.

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

What should a staff development plan address?

A

How staff skills will be utilized and developed.

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

What are key constraints to establish in project tracking?

A

Delivery date, budget, hardware, software, staff levels.

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

What is a milestone in project tracking?

A

A tangible achievement, such as completed software modules or documents.

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

What should be done when a problem arises in a project?

A

Identify the issue, initiate a solution, and revise constraints or schedules if needed.

17
Q

Why are time estimates for software projects often unreliable?

A

Each project is unique, uses different technologies, and previous estimates may not apply.

18
Q

Name two common scheduling tools used in project management.

A

Microsoft Project, Google Sheets.

19
Q

What are the ideal time frames for dividing project tasks?

A

Tasks should be between 1 to 10 weeks.

20
Q

What percentage of project effort is usually spent on planning?

21
Q

What percentage of effort is spent on system testing?

22
Q

What is the industry standard software output per developer per year?

A

~1000 lines of code (LOC) per year.

23
Q

What are the three project types in COCOMO?

A

Simple, Moderate, Embedded.

24
Q

What is the formula for estimating effort in Basic COCOMO?

A

Effort = a(KLOC)^b (where a and b depend on project type).

25
What are some limitations of Basic COCOMO?
Doesn’t consider hardware, programmer skill, or modern tools.
26
How does FPA estimate project size?
Based on user-perceived functionality, independent of language or style.
27
What are common categories used in FPA?
Outputs, inputs, inquiries, internal files, external interfaces.
28
What are the limitations of FPA?
Does not account for algorithm complexity or estimator bias.
29
What is the key feature of a Gantt chart?
Tasks are represented by horizontal bars; dependencies are shown with arrows.
30
What do diamonds represent in a Gantt chart?
Milestones and deliverables.
31
What does a PERT chart highlight?
Task completion, critical paths, and dependencies.
32
Name three types of risks in software projects.
Project risks, product risks, business risks.
33
Give an example of each type of risk.
* Project risk: Staff turnover * Product risk: Third-party tool failure * Business risk: Competitor releases a similar product
34
What are the four steps in risk management?
Risk identification, risk analysis, risk planning, risk monitoring.
35
What are two key aspects of risk analysis?
Probability of occurrence and cost of recovery.