Project Management and Planning Flashcards

1
Q

What is a good management?

A

Not a buffet. All are required, all are important and all have equal weight.

Effective management does not simply mean telling people what to do, not in software engineering.

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

Characteristics of good management?

A
Effective
Consistent
Respectful
Inclusive
Honest
Transparent
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Hierarchy of Human Needs?

A
Self-Realization
Esteem Needs
Social Needs
Safety Needs
Physiological Needs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Self-Realization?

A

Personal development, achievement, attainment

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

Esteem Needs?

A

The need to feel included respected, appreciated, acknowledgement

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

Social Needs?

A

The need to be part of social group

Inclusivity

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

Safety Needs?

A

Physical and mental safety

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

Physiological Needs?

A

Food, sleep

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

Jelled Teams?

A

Group of people so strongly knit that the whole greater than the sum of the parts

Probability of success goes up dramatically. The team can become almost unstoppable.

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

Factors that Influence Teamwork?

A

Informal Teams
Self-Organizing Teams
Hierarchical Groups
Difference in technical ability is a major challenge

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

Informal Teams?

A

Ad-Hoc, formed with a specific goal, tend to decide by consensus

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

Self-Organizing Teams?

A

Cross-functional team of people who collectively are responsible for all of the work necessary to produce working.
Essential in SCRUM

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

Hierarchical Groups?

A

Top down “instructions”
(or orders if you are in the army)
Rarely works for complex software engineering

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

Factors that affect communication?

A
Group Size
Group Structure
Group Composition
Physical Work Environment
Communication Channels
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Risk Areas?

A

Project
- Affect the project schedule or resources

Product
- Affect the suitability, quality or performance of the software being developed

Business
- Affect the organization developing or procuring the software

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

Risk Management Process?

A

Risk Identification
Risk Analysis
Risk Planning
Risk Monitoring

17
Q

Risk Identification?

A

Identifies project, product and business risks

18
Q

Risk Analysis?

A

Assesses the risk probability and impact

19
Q

Risk Monitoring?

A

Ensures risks are continuously monitored and reassessed

20
Q

Types of Risks?

A
Estimation Risks
Organizational Risks
People Risks
Requirement Risks
Technology Risks
Tools Risks
Integration Risks
21
Q

Risks Probability?

A

Measures the likehood that the risk will affect the project

22
Q

Risk Impact?

A

Measures the possible impact on the project

23
Q

Risk Planning

A

Mitigation Strategies
Avoidance Strategies
Minimization Strategies
Contingency Strategies

24
Q

Avoidance Strategies?

A

Aims to reduce the probability that the risk will occur

25
Q

Minimization Strategies?

A

Aim to reduce the impact of the risk should it materialize

26
Q

Contingency Strategies?

A

Describe how the team will proceed should the risk materialize

27
Q

Risk Monitoring? (Longer Def)

A

The project must be continuously assess for emerging risks in each risk area: product, project and business

28
Q

Risk Analysis Tags?

A

Risk Probability

Risk Impact

29
Q

Risk Probability Tags?

A

Very high (Red)
High (Orange)
Medium (Yellow)
Low (Gray)

30
Q

Risk Impact Tags?

A
Catastrophic Impact (Red)
Serious Impact (Orange)
Tolerable Impact (Yellow)
Insignificant Impact (Gray)
31
Q

The development process is planned in advance and documented in a project plan?

A

Project Plan Structure
Scheduling
Estimation

32
Q

Project Plan must identify?

A

Resources Available
Work Breakdown
Development Schedule

33
Q

Project Plan Document?

A
Introduction
Project Organization
Risk Analysis
Hardware and Software Resources
Work Breakdown Structure
Project Schedule
Monitoring and Reporting Mechanism
34
Q

Sprints are?

A

Time-Boxed Iterations

35
Q

Timeboxing is essential?

A

In establishing the work-in-progress (WIP) limit and establish velocity

36
Q

Forces the team to?

A

Prioritize features and avoid unnecessary polishing or gold-plating.

37
Q

Software Pricing Factors?

A
Contract
Uncertainty of Cost Estimate
Financial Health
Market
Volatility