5 Written questions
5 Matching questions
- % of time in analysis phase (industry std.)
- group cohesiveness
- % of time in design phase (industry std.)
- technical lead
- scope creep
- a when new requirements are added to the project after the original project scope was defined and "frozen"
- b 35%
- c the attraction that members feel to the group and to other members
- d person who oversees the progress of a group of programmers and more technical staff memebers
- e 20%
5 Multiple choice questions
- Size (functionality), time, money
- a document that tracks potential risks along with an evaluation of the likelihood of the risk and its potential impact on the project.
- dynamic schedule that records and keeps track of all of the tasks that need to be accomplished over the course of the project
- analysts and users proceed sequentially from one phase to the next.
- assign unrealistic deadlines, ignore good efforts, create a low-quality product, give everyone on the project a raise, make an important decision without the team's input, maintain poor working conditions
5 True/False questions
timeboxing → sets a fixed deadline for a project and delivers the system by that deadline no matter what, even if functionality needs to be reduced
% of time in planning phase (industry std.) → 20%
planning stage approach → more accurate three-step process for determining estimated size of new system.
% of time in implementation phase (industry std.) → 30%
4 steps to project management → estimate project time frame, develop work plan, staff the project, coordinate project activities