LM6-CH4 PP

What are the three main targets of project resource planning?

Human Resources; Methodologies & Processes; Tools and Equipment

T/F: Project resource planning includes 3 main targets: Human Resources, Methodologies & Processes, Tools and Equipment.

TRUE

Project resource planning includes 3 main targets: [blank], [blank], [blank].

Human Resources; Methodologies & Processes; Tools and Equipment

Why should all three resource types be merged?

To form a single combined resources plan.

T/F: All three types should be merged into a single combined resources plan.

TRUE

All three types should be merged into a single [blank] resources plan.

combined

Who are the most important resource?

Team members.

T/F: Team members are most important resource.

TRUE

Skilled people must be viewed as “[blank] [blank]”.

human capital

During planning, what do Software Managers focus on?

The recruiting effort and timing of hiring the appropriate people.

T/F: Software Managers focus on the recruiting effort and timing of hiring the appropriate people during planning.

TRUE

Software Managers focus on the [blank] effort and timing of hiring.

recruiting

What should be specified for each task’s people needs?

Required technical skills, experience, non-technical skills, temperament and traits.

T/F: Based on task type, specify the: required technical skills, required experience, required non-technical skills, required temperament and personal traits.

TRUE

If suitable recruits can’t be found, what relief may be sought?

Schedule relief, functional content reduction, or staged releases.

T/F: Should the manager not find the right recruits, the manager may need to seek relief in terms of schedule, functional content, or staged releases.

TRUE

How much time should be added for onboarding recruits?

An extra month or so.

T/F: Always add an extra month or so for persons who need to be recruited and brought on board.

TRUE

Temporary employees are often hired for what reason?

Their immediate technical skills.

T/F: Temporary employees are often hired for their immediate technical skills and not their employee retention and career development potential.

TRUE

What does Table 4.1 (skills description) not include?

The timing at which resources are acquired or used.

T/F: It does not layout the timing at which the resources are acquired or used.

TRUE

What distinguishes direct vs indirect project activities?

Direct lead to deliverables; indirect do not.

T/F: Direct: project activities that lead to customer deliverable. Indirect: project activities don’t lead to a customer deliverable.

TRUE

Direct activities lead to a customer [blank].

deliverable

What does a human resource plan matrix indicate?

Availability of needed skills at the appropriate time.

T/F: A human resource plan matrix indicates the availability of the needed skills at the appropriate time.

TRUE

What does a people hiring matrix show?

Each human resource and the time period associated (including assimilation time).

T/F: A project hiring plan, in the form of a people hiring matrix or bar chart, indicates each specific human resource and the time period for which that person is associated with the project (including assimilation time).

TRUE

Management should monitor what for employees?

Morale and personal growth.

T/F: Management should monitor the morale of employees and ensure personal growth.

TRUE

Why avoid hiring at top of compensation range?

To allow raises without requiring a promotion.

T/F: Try not to bring in individuals at the top of the compensation range for their position.

TRUE

Software Development Process definition?

An ordered set of defined activities for defining requirements, designing, coding, and release.

T/F: Software Development Process: an ordered set of defined activities that describe the defining requirements, designing, coding, and release for a software artifact.

TRUE

Software Methodology definition?

A set of rules and principles to achieve a specific goal and accomplish a specific task.

T/F: Software Methodology: a set of rules and principles defined to achieve a specific goal and to accomplish a specific task in the development or support of software.

TRUE

Process vs methodology: what vs how?

Processes define what; methodologies specify how.

T/F: Processes are more stable, structural: they define what needs to be done; methodologies specify how the steps in a process are to be carried out.

TRUE

Why ensure team understands methodologies?

To decrease methodology wars, missed deadlines, and poor quality.

T/F: Be sure team members understand the defined methodologies for the project. This will decrease the chance for methodology wars, missing project deadlines, and producing poor quality software.

TRUE

What can lack of well-understood methods cause?

Missing schedules, poor quality, demoralized teams, failures.

T/F: Many project failures have occurred when the confusion created by a lack of well-understood processes and methodologies resulting in missing schedules, poor product quality, demoralized teams, etc.

TRUE

List the SDLC phases used in planning.

Requirements processing; Design; Implementation and programming; Testing; Product release.

T/F: Project manager will determine the overall process in some form of all the SDLC phases: Requirements processing, Design, Implementation and programming, Testing, Product release.

TRUE

What must the project plan describe about activities?

Which of and how much are part of the specific project.

T/F: A project plan must describe which of and how much of these activites are part of the specific project.

TRUE

When is no requirements process needed?

When project is well-defined and specifications are reviewed and signed off.

T/F: Is project well-defined and req specifications have been reviewed and signed off? Yes → No requirements process needed.

TRUE

If not well-defined, what must be established for requirements?

How requirements will be gathered, documented, reviewed, and agreed upon.

T/F: Establish processes for how requirements will be gathered, documented, reviewed, and agreed upon.

TRUE

What should requirements processes include?

Management of changes and modifications; education on process and methodology.

T/F: Processes should also incorporate management + change modifications. Include education on process and methodology.

TRUE

What are candidate design process activities?

Architectural, high-level, low-level design, analysis, review, change/impact management.

T/F: Design Process Planning Types of activities to include: Architectural design; High-level application design; Low-level application design; Design analysis; Design review; Design change/impact management.

TRUE

What must accompany each design activity?

A well-defined methodology and education plan.

T/F: For each activity, assign a well-defined methodology and education plan.

TRUE

What should implementation planning include beyond coding?

Documentation, standards, reuse management, reviews, unit testing.

T/F: In addition to code development, should include document and publication development activities.

TRUE

Acquired code standards should do what?

Match the project’s definition/standards.

T/F: Standards of acquired material should match that of project’s definition.

TRUE

Why is integration of acquired software hard?

It is both a management and a technical issue.

T/F: Is both a management (doesn’t always merge smoothly) and technical issue (policing of old/new interfaces).

TRUE

What does test process planning include?

Overall test process, tools, skills, schedule; test types, owners, and order.

T/F: May not include methodology but must include overall test process, tools utilized, skills required, and schedule. Includes which types of testing will be conducted, by whom and in what order.

TRUE

Define test scenario.

A description of interactions between system and external agent to accomplish a task/goal.

T/F: Test scenario: a description of a set of interactions between the system and an external agent to accomplish a desired user task or goal.

TRUE

Define test case.

A description of a specific interaction with defined inputs and expected outputs; developed from a scenario.

T/F: Test case: a description of a specific interaction between the system and external agent; developed from test scenario.

TRUE

Define test script.

A test case written in a language used directly by a test tool.

T/F: Test script: a test case written in a language that me used directly by some test tool to conduct actual test.

TRUE

What activities are in product release planning?

Integration, packaging, installation; order, release, shipment management.

T/F: Product Release Planning Types of Activities: Integration, packaging, installation; Product order, release, shipment management.

TRUE

If install mechanism not in requirements, then what?

It must be specified during product release planning.

T/F: If install mechanism not outlined in requirements must be done so here.

TRUE

What are key cross-functional processes?

Configuration management; Outsourcing/Procurement; Quality assurance; Change management; Reporting/Escalation.

T/F: Cross-Functional Process Planning Activities include: Configuration management; Outsourcing / Procurement management; Quality assurance; Project change management; Project reporting / escalation process.

TRUE

Configuration Management definition.

Discipline of systematically managing changes to software artifacts.

T/F: Configuration Management: discipline of systematically managing changes to software artifacts.

TRUE

Project Change Management definition.

Structured process for managing changes to scope, schedule, budget, or objectives.

T/F: Project Change Management: structured process for managing changes to project scope, schedule, budget, or objectives.

TRUE

When are tools identified and prepared?

Once process and methodology are defined; include training and installation.

T/F: Once the process and methodology are defined, tools are identified, prepared, and selected to help the team follow through efficiently.

TRUE

List common hardware resources.

Desktop computer, servers, printers, network equipment.

T/F: Hardware tools: desktop computer, servers, printers, and network equipment.

TRUE

List common software platform resources.

Operating systems, database systems, middleware systems, browsers.

T/F: Software: Operating systems, database systems, middleware systems, browsers.

TRUE

List categories of project tools.

Development, requirements, design, documentation, test, support, management & general.

T/F: Development and Implementation tools: compilers, editors, and debugging aids; Requirements Management tools; Design tools; Documentation tools; Test tools; Support tools; Management & General.

TRUE

Why plan processes & methodologies as resources?

They are intellectual capital and must be included.

T/F: Processes & Methodologies must be planned for an included as a resource.

TRUE

Intellectual capital definition.

Knowledge that is considered an asset and ultimately has financial value.

T/F: Intellectual capital: knowledge that is considered an asset and ultimately has financial value.

TRUE

What increases likelihood of smooth project flow?

Spending more time and effort on planning.

T/F: The more time and effort spent on planning, the more likely the rest of the project will flow smoothly.

TRUE

What do required resources depend on?

Deliverables, tasks, schedule, and project goals.

T/F: Required resources depend on: deliverables, tasks, schedule, and project goals.

TRUE

What does a combined resource matrix exhibit?

Phases, requirements, design, implementation, testing, release, and support plans.

T/F: The combined resource matrix exhibits project phases, requirements, design, implementation, testing, release, and support plans.

TRUE

Define outsourcing vs insourcing.

Outsourcing: moving work to external sources; Insourcing: bringing external human resources to perform work.