Lecture 3 - Establishing Software Project Management Foundations II Flashcards

1
Q

What are the three major responsibilities of a project manager?

A

feasibility study, planning, execution monitoring and control

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

A study made before committing to a project is a…

A

feasibility study

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

advocacy needed to build enthusiasm for a project and convincing organizations to undertake a project with many risks is a difficulty of?

A

feasibility studies

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

Breaking down work into parts to assign to team members; anticipate problems; preparing solutions to problems is related to which responsibility of a project manager?

A

project planning

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

The project plan is used to communicate how the work will be done to the project team and customers, as well as assess progress on project

A

True

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

What are the 5 important activities of project planning

A

Estimation
Scheduling
Staffing
Risk management
miscellaneous plans

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

What are the 4 elements involved in project execution

A

Monitoring
Controlling
Innovating
Representing

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

TF: Monitoring is checking on progress, revising plans

A

True

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

TF: Controlling is coming up with solutions when problems emerge

A

False. It’s taking action to remedy hold-ups

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

TF: Innovating is coming up with solutions when problems emerge

A

True

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

TF: Representing is liaisoning with client, users, developers, and other stakeholders

A

True

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

In project control cycle, raw details such as ‘20 user stories developed by team 3’ is called…

A

data

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

In project control cycle, data processed to produce something meaningful and useful such as ‘productivity is two user stories per day’ is called…

A

information

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

In project control cycle, the sentence ‘we will not meet the target of delivering 50 user stories by Nov. 15’ is an example of…

A

comparison. We are comparing objectives (delivering 50 user stories) with goal (by Nov. 15)

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

In project control cycle, working out the probable outcomes of various decisions such as ‘if 2 more devs are brought onboard, how quickly can user stories get developed’ is called…

A

modelling

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

In project control cycle, carrying out the remedial actions that have been decided upon is called…

A

implementation

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

What are the elements of Requirement Analysis?

A

Requirement elicitation (gathering)
Analysis

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

What is Requirements elicitation in Requirement Analysis?

A

‘What does the client need’

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

What is Analysis in Requirement analysis?

A

converting customer requirements into equivalents that devs can understand

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

What is Architecture design in Software Development Life Cycle?

A

Define components of the system
- hardware
- software
- organisational

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

What comes out of Architectural Design in Software Development Life Cycle?

A

Software requirements

22
Q

Architectural design in Software development life cycle is based on what?

A

system requirements

23
Q

What is Detailed Design in Software Development Life Cycle?

A

each component is made up a number of software units that can be tested separately

24
Q

What does Code and Test involve in Software Development Life Cycle?

A

coding and testing each individual components

25
Q

What is Integration in Software Development Life Cycle?

A

putting components together and testing them together to see if they meet overall requirements

26
Q

What is qualification testing in Software Development Life Cycle?

A

Testing system to check whether all requirements have been fulfilled (not just software)

27
Q

What is installation in Software Development Life Cycle?

A

Process of making new system operational.
- Setting up standing data and system parameters
- Installing on operational hardware platforms
- etc.

28
Q

What is Acceptance support in Software Development Life Cycle?

A

maintenance and enhancement

29
Q

What is Software Project Contract?

A

Software Acquisition

30
Q

TF: Software acquisition is the same thing as software project management.

A

False

31
Q

TF: Software project acquisition concerned with legally binding issues involved in contracting with an external customer

A

True

32
Q

What are the 4 elements involved in Software Project Contract

A
  • Fixed Price
  • Time and materials
  • Cost plus fixed fee
  • Cost plus incentive fee
33
Q

What are the two types of contractual agreement?

A

Informal and formal

34
Q

TF: Informal contractual agreement is a statement of understanding between the project manager, and an internal customer

A

True

35
Q

TF: Formal contractual agreement is a verbal contract between your organization and the acquirer’s organization.

A

False. It is a legal contract

36
Q

How are informal contracts documented?

A

Documented in Memos of Understanding (MOUs)

37
Q

How are formal contracts documented?

A

in the form of a Statement of Work (SOW)

38
Q

TF: Making current activity visible as well as establishing guidelines is not a benefit of Measurement

A

False

39
Q

TF: Measurement allows us to predict outcomes and change processes

A

True

40
Q

Measurement does not allow us to establish quality targets and improve

A

False

41
Q

What are the three things Measuring is concerned with?

A

Collecting, Validating, Analyzing project status information

42
Q

TF: Controlling in a project is concerned with applying corrective action when status does not conform to planned status

A

True

43
Q

What are the two status’ Controlling is concerned with? Provide example for each

A
  • status of work products (qantity/quality of products)
  • status of development process (schedule, budget, resource, risk factors)
44
Q

What should be measured and controlled? (7)

A
  • Product features
  • Quality attributes
  • Effort
  • Schedule
  • Cost
  • Progress
  • Risk
45
Q

What does measuring product features entail?

A

checking requirements implemented and that they work

46
Q

What does measuring quality attributes entail?

A

checking defects, reliability, availability, response time, etc.

47
Q

What does measuring effort entail?

A

measuring amount of work expended for various activities

48
Q

What does measuring schedule entail?

A

checking achievement of objectively measured milestones

49
Q

What does measuring cost entail?

A

measuring expenditures on various kinds of resources

50
Q

What does measuring progress entail?

A

measuring work products completes, accepted and baselined

51
Q

What does measuring risk entail?

A

checking status of risk factors, mitigating activities

52
Q

TF: Software being cheap, reliable, testable, secure, and maintainable is what makes quality software

A

False. There is no clear-cut answer (depends on stakeholders, type, etc.)