Software Project Management

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/74

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

75 Terms

1
New cards

The existential questions (Critical Management Questions)

  • Why is the system being developed?

  • Is there a good business case for initiating the project?

  • Should it continue or be terminated?

2
New cards

The people side (soft side of software engineering) (Critical Management Questions)

  • Who is on the team?

  • do we have effective high performing teams?

  • how is our team/project structured?

  • what is our decision making process?

3
New cards

How much of each resource is needed? (Critical Management Questions)

People are the most important resource, selection ,hiring, and retention

4
New cards

Which life cycle model will we use? (Critical Management Questions)

Iterative and/or incremental approaches

5
New cards

Setting and managing expectations (Critical Management Questions)

  • What is the scope of the product?

  • When will it get done?

  • How much is it gonna cost?

The customer will change the scope of the project (requirement volatility) which will impact the schedule and cost.

6
New cards

How will the work be done? (Critical Management Questions)

  • which organizational assests will be used?

  • which Engineering processes? XP, TDD, Peer reviews…

  • Which management process will be used? Scrum, EVM, burndown charts…

7
New cards

Communications (Critical Management Questions)

  • Do we have good communication with our customer and our staff?

  • Who is responsible for implementing a module?

8
New cards

How are we managing risks? (Critical Management Questions)

  • Have you gone through a risk identification process?

  • Risk monitoring?

  • Contingency plans, is there a backup plan?

9
New cards

According to Reifer, Software management is

  • the act of motivating people

  • to accomplish desired work-related goals and objectives

  • using available resources in the most efficient and effective manner.

10
New cards

Healthcare.gov was mostly a…

management failure, there almost no management at all

11
New cards

What does it mean by “The problem is management”

  • when a project is cancelled, management failure is usually the root cause

  • There are lots of problems that will give us grief, with known solutions. We simply do not use them.

12
New cards

What causes today’s major problems within military software

Management problems rather than technical

13
New cards

(1/10) Most effective way of planning?

Use a work breakdown structure (WBS) as your primary planning tool

14
New cards

(2/10) How can you make sure you’re no over promise and under delivering?

Establish reasonable budgets and schedules for the effort required

15
New cards

(3/10) How can we solve and avoid scheduling issues and adhere to deadlines

Use critical path analysis to devise the shortest possible schedule

16
New cards

(4/10) What is the most effective way of identifying defects?

Embrace peer reviews as your primary appraisal methodology

17
New cards

(5/10) How can we gauge how much effort and time will be required to finish tasks?

Use rate of progress charts to get a handle on what it will take to finish tasks

18
New cards

(6/10) How does one know when to release a product

Embrace defect metrics to determine when it is reasonable to release the product.

19
New cards

T/F You dont have to fix all the bugs before the release of a product

True

20
New cards

(7/10) What can be used to gauge how much it will take to complete the effort?

Rely on cost and schedule-to-complete estimates to get a handle on what it will take to complete the effort.

21
New cards

(8/10) What needs to be tracked prior to release?

Track open issues and actions to their culmination prior to releasing the product. You should closely monitor and follow through on any outstanding problems, tasks, or actions that need to be resolved or completed before the product is ready for release or launch.

22
New cards

(9/10) What needs to be checked to ensure product meets user expectations?

Check quality often to ensure the product meets user expectations

23
New cards

(10/10) How can resources be managed effectively when issues arise?

Use risk management techniques to determine priorities so that you can use resources effectively once issues start arising.

24
New cards

What a work breakdown structure (WBS)?

An enumeration of all work activities in hierarchy

25
New cards

How is a WBS oriented?

  • Can be task-oriented

  • Can be product-oriented

  • likely hybrid

26
New cards

How is work organized in a WBS?

Organizes work into work packages of short, manageable tasks.

27
New cards

What is the typical level of effort required according to WBS?

8-80 person-hours of effort(1-10 days)

28
New cards

T/F The WBS is used to assign responsibility for tasks

TRUE

29
New cards

What estimates are required by an item in the WBS?

Time and cost estimates are needed b each item in the WBS.

30
New cards

T/F For software projects, effort and cost are largely the same

TRUE

31
New cards

What creates a disconnect between managers and programmers?

Their definition of success

32
New cards

In one research study of a project that failed to meet its estimates, the management saw it as a ___ and the technical participants saw it as the most ____ project they had ever worked on

failure, successful

33
New cards

What is Estimating

The process of forecasting or approximating the time and cost of completing project deliverables

34
New cards

What parameters, other than time and cost need to be estimated?

  • size – lines of code, function points, etc

  • critical resources

35
New cards

T/F Software project cost is largely driven by effort.

TRUE

36
New cards

T/F Schedule and effort are the same when estimating.

FALSE

37
New cards

What are the two major classes of estimating

  • Top-down

  • bottom-up

38
New cards

T/F Top-Down estimating gives a rough estimate

TRUE

39
New cards

Top-Down estimating is usually done by ____

Senior Management

40
New cards

Bottom-Up estimating is usually done by _____

the people who are doing the work

41
New cards

Bottom-Up estimating is based on ______

Work Breakdown Structure

42
New cards

What is aggregating expert judgment?

Combine estimates from a number of experts. You could calculate the average or median of the individual estimates

43
New cards

How do you overcome the influences of assertive experts and authority figures when aggregating judgments?

The practice of the Wideband Delphi method

44
New cards

Wideband Delphi method is when ____

Experts estimate anonymously iteratively until convergence

45
New cards

T/F You should be pessimistic in your estimates

TRUE

46
New cards

the student syndrome - Starting at the last minute is an example of ____

Wasting the safety

47
New cards

Multitasking is an example of ____

Wasting the safety

48
New cards

T/F Dependencies between steps cause delays to accumulate and advances to be wasted

TRUE

49
New cards

User Story (Agile methods)

Describes functionality that will be valuable to either a user or purchaser of a system.

50
New cards

What are the three components of a user story?

  1. Card

  2. Conversation

  3. Confirmation

51
New cards

In user story, the card is _____

written description of the story used for planning and as a reminder

52
New cards

User story conversations are ___

about the story that serve to flesh out details of the story

53
New cards

A user story confirmation are the ___

details that can be used to determine when a story is complete.

54
New cards

T/F A user story is a promise to have a discussion in which not every detail needs to be included.

TRUE

55
New cards

What are Story points?

the unit in which user stories are normally estimated in

56
New cards

T/F Story points are not artificial measures of effort, meaning they are a direct measure of effort (i.e. hours, minutes, weeks)

FALSE,

  • Story points are artificial measures of effort

  • They are not a direct measure of effort, such as hours

57
New cards

T/F Humans tend to be better at making relative or comparative estimations than they are at providing precise, absolute values. In Agile estimation, this principle is leveraged by comparing new user stories to existing ones.

TRUE

58
New cards

Y/N Do story point estimates change because of experience?

No

59
New cards

Y/N In agile project management and estimation, is it common for the absolute accuracy of estimations to be less important than maintaining consistency among the estimations?

Yes, the primary goal of estimation is not to achieve perfectly accurate estimations, so long as they are consistent.

Example:

  • if Feature A is estimated as twice as complex as Feature B, this relative comparison should hold true across the board.

60
New cards

Y/N Does velocity, after a few sprints, tend to stabilize until and unless the team is changed?

Yes

61
New cards

Iron Triangle - Projects have imposed constraints of

  1. scope (features, requirements)

  2. cost (resource, effort)

  3. time (schedule)

62
New cards

Y/N With regards to the Iron Triangle, can you change one constraint without affecting one or both of the others?

No, you can “fix” all three at the same time

63
New cards

Karl Wiegers (1996) suggests there are really 5 interrelated project dimensions

  1. scope

  2. schedule

  3. cost

  4. staff

  5. quality

64
New cards

T/F According to Goldratt, multitasking is probably the biggest killer of lead time.

TRUE

65
New cards

Y/S Is there an inverse relationship between the number of simultaneous projects and productivity?

Yes

66
New cards

What is the required time commitment towards a specific team, in order to be considered as “full time”?

90%

67
New cards

What does it mean by providing 50-90% towards a team

Part time, “This is my home team but I have other commitments, too”

68
New cards

T/F Less than 50% means not a team member

TRUE, “I can support you guys from time to time, but I’m not part of your team and you can’t always count on me”

69
New cards

How can you maintain performance despite having to multitask?

The key to performance is focusing on the high-priority tasks first.

70
New cards

Plans and forecasts that are unrealistically close to best-case scenarios can be described by the _____

The Planning Fallacy

71
New cards

How can we mitigate the planning fallacy?

TBD

72
New cards

T/F The larger the software the higher the probability of the software project being cancelled

TRUE

73
New cards
74
New cards
75
New cards