Exam 2: Project Selection and Management

Micah is a fairly new project manager.He estimated for a project plan (on the planning phase)that the project would cost $50,000 and take 20 weeks.According to the margin of error guidelines for well-done estimates,that could range from:

A classic planning mistake mentioned in the textbook is motivating employees with financial rewards instead of recognition and genuine thanks.

Which would generally NOT be taken into consideration for project portfolio management in an organization?

What can you do to manage scope creep?

System prototyping is BEST characterized as:

If the skills required by a project cannot be met by the available project team,which would probably NOT be a reasonable solution?

Scope creep is when new requirements are added to the project after the original project scope was defined and 'frozen'.

Extreme Programming (XP)stresses customer satisfaction and teamwork.

Throwaway Prototyping balances the benefits of well-thought-out analysis and design phases with the advantages of using prototypes to refine key issues before a system is built.

Tatiana is developing a staffing plan for a project.Which of the following would she NOT consider in developing such a staffing plan?

Using industry standards,the general estimated project time for the Implementation phase is 15%.

If you had a project with very clear requirements;familiar technologies;not super complex;reliable;a very long time schedule and where the need for schedule visibility is low - the best methodology might be Extreme programming

The science (or art)of project management is setting a schedule and sticking to it no matter what - even if that includes working weekends and adding staff to reach the deadline on time.

Which of the following methodologies might be most appropriate if you have a system project with: unclear user requirements;unfamiliar technologies;very complex;must be reliable;a short to medium time schedule and the schedule visibility is somewhat important?

What is the difference between systems prototyping and throwaway prototyping methodologies?

CASE stands for:

Which of the following is NOT a classic planning mistake?

Which of the following would BEST describe "familiarity with technology"?

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;reasonably reliable;a very long time schedule and the schedule visibility is not important?

A two-person team has single line of communication;a three-person team will have three lines of communication;a four-person team will have six lines of communication.A team with n members will have: