LM15 (TEXT & PP) - 5 STARRED

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/49

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.

50 Terms

1
New cards

It is well recognized that software projects are particularly prone to changes, in large part because there is a general belief that software can be easily ____________.

modified

2
New cards

T/F: Maleability in software is in fact both a strength and a weakness: Changes may be made in software, but must be implemented with care.

TRUE

3
New cards

Define Change Control Process

A sequence of activities used in the tracking and managing of a change request from its inception to its closure.

4
New cards

The worst situation occurs when changes are allowed without proper control. To prevent this type of “change control chaos,” the software project team should develop and follow a:

change control process.

5
New cards

Every change to the product or to the process should start with a _____________, which represents the first, formally defined version of a product or process, and go through a change control process.

baseline

6
New cards

Define Change Request Form

A formal method for submitting a change request, may be a paper-based form or part of an online system.

7
New cards

What should a change request form include?

  • Requester’s name

  • Request date

  • Request description

  • Request reason

  • Request priority

  • Preferred completion date

  • Funding source

  • Areas affected by change

8
New cards

Once the request form is filled out, it should be submitted to a “_______.”

catcher

9
New cards

Define change request catcher.

A handler designated to formally take charge of the request.

10
New cards

Who might serve as a change request catcher?

The software project manager, the Release Management Council, or a special change request administrator.

11
New cards

Define change impact analysis.

The list and description of affected items generated from the review and assessment of a change request submission.

12
New cards

The change impact analysis will list and describe the items that are affected, including the following areas of consideration:

Some changes help process product content and marketing strategies

  • Schedule

  • Cost

  • Human resources

  • Processes and tools

  • Product content and size

  • Product marketing strategy

13
New cards

Sometimes the change control process also needs to take into account how a change request affects the:

customers’ work flow and work environment.

14
New cards

T/F: Software impact analysis identifies the effects of a software change request.

TRUE

15
New cards

Why is a measurement scheme needed for change requests?

So each change request may be gauged in relation to other change requests.

16
New cards

How can one quantify the measurement of schedule impacts of a change request?

By designating a value range of 1 to 4, where:

  • 1: means a schedule impact of 1-2 days

  • 2: means 1-2 weeks

  • 3: means an impact of 1-2 months

  • 4: means an impact exceeding 2 months

17
New cards

How can one quantify the measurement of personnel impacts of a change request?

May also be designated with values ranging from 1 to 4, where:

  • 1 means a slight assignment change to one person

  • 2 means two to three people are involved in the change

  • 3 means one-fourth of all team members are involved

  • 4 means half or more of the team members are involved

18
New cards

How can one quantify the measurement of personnel cost impacts of a change request?

May be directly quantified, by using the schedule impact, the personnel impact, and the conversion of those impacts into dollars.

  • A schedule impact of 1 and a personnel impact of 2 would convert to (2 days × 3 people) = 6 people-days of impact.

  • 6 people-days × z $/person-day = 6z dollar of cost impact.

19
New cards

After each impacted area is quantified, the change requests can be compared by _____ and possibly _______.

area; ordered

20
New cards

Furthermore, each impacted area may be assigned a __________.

numerical weight

21
New cards

What should happen when a project manager decides to reject/deny a change request?

The rejection must be communicated back to the requestor, along with a reason for the rejection.

22
New cards

What should happen when a project manager decides to accept a change request?

Mark Form Schedule Perform Track Close

  • Mark and assemble all affected items.

  • Formulate a plan for performing the change.

  • Schedule, perform, track the actual change activity.

  • Close the change request upon completion, and notify the requestor.

23
New cards

What should happen when a project manager decides to accept a change request but is unable to accommodate it with the current release date or budget?

The change request is held for scheduling into a future release and the requestor is informed.

24
New cards

T/F: A small change in a software artifact can have huge ramifications for both the end product and the work effort required to develop that product.

TRUE

25
New cards

Complications come not necessarily from the initial change itself, but from the “_________”—the effect of related work that can dramatically affect both schedules and costs.

ripple effect

26
New cards

Another important aspect of change requests that the software project managers need to be aware of is the requests’ psychological effect on the team. Why?

  • Constant flip-flopping leads project team to not perform any changes until the requestor can make up his or her mind.

  • Changes concentrated to a specific functional area, can cause the project team to feel helpless and demoralized.

27
New cards

Who is responsible for shielding the project when a multitude of change requests keep coming?

The software project manager

28
New cards

What are the two types of change control processes?

Product changes, process changes

29
New cards

Explain product changes

Large products and lengthy development schedules almost always (force) experience changes:

  • Technology improvements “forces” changes

  • Competition “drives” changes

  • Customers’ new demands “requires” changes

  • Developers’ new views “leads” to changes

30
New cards

Technology improvements “_________” changes

forces

31
New cards

____________ “drives” changes.

Competition

32
New cards

Customers’ ___________ “requires” changes

new demands

33
New cards

Developers’ _________ “leads” to changes

new views

34
New cards

Explain process changes.

Product changes may lead to corresponding process changes:

• Users’ business process changes

• Development/support process changes

35
New cards

Changes must be _____________.

controlled

36
New cards

A set of ____________ needs to be maintained.

information; hence the change request form

37
New cards

A sequence of ___________ must be followed.

activities (process); hence the change request process

38
New cards

The information related to each change is kept in a three part “form”:

  (A)  Change request

  (B)  Change impact analysis

  (C)  Change status

39
New cards

Explain a change request.

To manage changes, information related to the change must be tracked, (as a Change Request Form - paper or electronic).

40
New cards

T/F: Before a change request is worked on, someone must analyze the request.

TRUE

41
New cards

What cautions should be had when conducting a change impact analysis?

  • A development organization with a tight schedule will not automatically have resources to perform this analysis.

  • A development organization may not have a change request process.

42
New cards

What does a change impact analysis typically include?

Impact of change: technical, resource, schedule, business

43
New cards

What does a change impact analysis often lead to?

  • Reassessment in schedule, resource, cost

  • Feature/Functionality Reassessment: (business flow or competitiveness)

44
New cards

T/F: The impacts of a change impact analysis may be assigned different weights and “rolled” into a single impact number.

TRUE

45
New cards

The impact analysis information for each change request may be attached to the change request form and include:

– Who conducted the impact analysis

– What: impact analysis information, results, recommendation

– When: start / end dates of impact analysis

46
New cards

Explain change status.

As the change request moves from requestor to analyst, and finally to implementation, the information must be tracked until the request comes to closure:

  • Rejected:  rejection date and reason

  • Accepted:  expected work start date

  • In-Progress:  expected completion date and by whom

  • Completed:  completion date and by whom

47
New cards

To _______ the Change Request, there must be a _______ that is followed.

control, process

48
New cards

___________ is a common occurrence if changes are not controlled.

Scope creep

49
New cards

Scope creep is a common occurrence if changes are not controlled resulting in:

•Missed schedule

•Cost overflow

•Low morale

50
New cards

What must be considered when implementing a change control process?

Whether you have the skilled human resources, tools, and financing to implement the change control process.

Explore top flashcards