SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Project Management Using Microsoft Project
Start Test
Study First
Subjects
:
certifications
,
microsoft-project
,
business-skills
,
it-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A logical relationship that states that for one project to begin - another must also be underway. For example - the writing of a business proposal must have begun in order for editing of the proposal to take place.
Start to Start
Drawing on Gantt (Project 2010)
Customize 'Quick Access Tool Bar'
'80 hour rule'
2. View -> Timeline check box. Shows timeline - but by default - nothing's on it. To add items - right click and 'add to timeline'.
Timeline (Project 2010)
d (Abbreviations Project 2010)
Gantt Chart Wizard (Project 2010)
'80 hour rule'
3. Task ribbon -> schedule section -> broken task icon. Reschedule incomplete work - etc.
File Name vs. Project name (Project 2010)
Team Planner (Project 2010)
Splitting tasks (Project 2010)
Fixed Work
4. Task ribbon -> 'inspect' button-> Inspect Task. It shows more details about highlighted task - including critical predecessor task. Very useful tool. Especially when resources are over allocated.
WBS Work Breakdown Structure
SNET
Inspect feature (Project 2010)
Calendars to consider
5. Add your resources names to critical tasks _______ via bar styles/text.
Reccuring Tasks
Fixed Duration
Splitting tasks (Project 2010)
Manually
6. Appears: wk means: week
Inspect feature (Project 2010)
w (Abbreviations Project 2010)
SNET
Form (Project 2010)
7. Appears: hr means: hour
File Name vs. Project name (Project 2010)
h (Abbreviations Project 2010)
'Hiding' columns (Project 2010)
Accessing 'Properties' (Project 2010)
8. Two critical tasks - both same duration - vying for one resource - who wins?
File Name vs. Project name (Project 2010)
Task with first ID
Bar Style (Project 2010)
Project Files (Project 2010)
9. Tables - charts - usage tables - and sheets.
Views (Project 2010)
Network Diagram best practices
m (Abbreviations Project 2010)
Initializing a Project (Project 2010)
10. It is NOT an exhaustive list of work. It is instead a comprehensive classification of project scope. Contains Sub-components - work packages (child of sub-component). Further work packages can be children of other work packages. Summary tasks are the
Terminal element
Project Files (Project 2010)
WBS Work Breakdown Structure
5 phases of project
11. The FILE name is what you see at the top of the screen - and is the raw name of the .mpp or .mpt FILE itself. The PROJECT NAME is set in the 'Properties' of the project. The project name will show up in reports - etc.
Reccuring Tasks
File Name vs. Project name (Project 2010)
Terminal element
Calendars to consider
12. Time delay. Sometimes - it's preferred to have lag shown as a task. You can assign costs to it - that way. Style sheets will indicate this.
Organizer (Project 2010)
Logical Relationships in PDM
Lag
Team Planner (Project 2010)
13. Shows closest thing to a 'resource gantt chart'. Shows tasks by resource. Also shows unassigned tasks - and unscheduled tasks. Allows for user-controlled scheduling.
Team Planner (Project 2010)
Duration
File Name vs. Project name (Project 2010)
Customize 'Quick Access Tool Bar'
14. Single Start - Single Finish. No 'danglers'. Everything must be connected. No loops.
Box Styles (Project 2010)
Task Type
Logical Relationships in PDM
Network Diagram best practices
15. No single activity or group of activities to produce a single deliverable should be more than 80 hours of effort.
16. Task calendar - resource calendar - base calendar.
PDM
Calendars to consider
Material resource
w (Abbreviations Project 2010)
17. Always preserve the number of hours to perform a task. Changing work when fixed will impact duration.
Start to Start
Fixed Work
Organizer (Project 2010)
Views (Project 2010)
18. Always preserve the number of people working on a task. Changing units when fixed will impact duration.
eh (Abbreviations Project 2010)
Fixed Units
Table (Project 2010)
File Name vs. Project name (Project 2010)
19. Gantt Chart with 'Entry' table on left.
DSM Design Structure Matrix
Fixed Units
Default view (Project 2010)
w (Abbreviations Project 2010)
20. File -> Options -> Scheduling --> Drop down for Decimal or Percentage.
Show Assignment Units as (Project 2010)
mo (Abbreviations Project 2010)
Calendar/ Working time (Project 2010)
The task which has the LEAST slack is more important - Min-slack wins
21. A compact - matrix representation of a system or project. The approach can be used to model complex systems in systems engineering or systems analysis - and in project planning and project management.
Team Planner (Project 2010)
Views (Project 2010)
Material resource
DSM Design Structure Matrix
22. Function key 5. You can go directly to ID - or 'date'.
Drawing on Gantt (Project 2010)
w (Abbreviations Project 2010)
GO TO (Project 2010)
Inspect feature (Project 2010)
23. File -> Options -> Quick Access tool bar. Examples: Tables and Vies - good stuff.
24. Tables are made up of fields.
Table (Project 2010)
Calendars to consider
eh (Abbreviations Project 2010)
Manually
25. efines units.
Inspect feature (Project 2010)
Material resource
Form (Project 2010)
The task which has the LEAST slack is more important - Min-slack wins
26. Responsibility Assignment Matrix.
GO TO (Project 2010)
Views (Project 2010)
Gantt Chart Wizard (Project 2010)
RAM
27. 1. Initiation 2. Planning 3. Execution 4. Monitoring & Control 5. Closing
ed (Abbreviations Project 2010)
Logical Relationships in PDM
RAM
5 phases of project
28. W = D + U Duration plus available resource units
GO TO (Project 2010)
Earned Value
Initializing a Project (Project 2010)
Work
29. The number of resources required to get the tasks/assignments completed.
Peak
Template (Project 2010)
Box Styles (Project 2010)
Summary tasks (WBS)
30. Tasks - resources - assignments - all have dialogs. Example: resource leveling. Project information dialog very important.
Accessing 'Properties' (Project 2010)
Dialogs (Project 2010)
Start to Finish (SF)
PDM
31. Start date - Current date - finish date - status date - schedule from - calendar - & priority (with project pro). Enterprise custom fields here too - if you're hooked into enterprise.
Project information dialog (Project 2010)
Table (Project 2010)
eh (Abbreviations Project 2010)
Start to Finish (SF)
32. Always preserve the duration of a task. Changing duration when fixed will impact work.
Template (Project 2010)
ew (Abbreviations Project 2010)
Task with minimum duration
Fixed Duration
33. Can be added to the ribbon - and it walks user through formatting of the gantt chart. Pretty cool.
Organizer (Project 2010)
Gantt Chart Wizard (Project 2010)
h (Abbreviations Project 2010)
'80 hour rule'
34. Default view in Network Diagram. Without LINK LABELS - you won't see lag time - etc. The term finish to start refers specifically to the logical relationship that exits between the activities that make up he entirety of the project in which it is det
Manually
Show Assignment Units as (Project 2010)
Finish to Start
Table (Project 2010)
35. Work divided by available resource units. Formula: D=W/U
Duration
Dialogs (Project 2010)
Template (Project 2010)
Task Type
36. Work - resource - cost.
Resource types
Gantt Chart Wizard (Project 2010)
Drawing on Gantt (Project 2010)
Template (Project 2010)
37. U = W / D Work divided by duration.
Form (Project 2010)
Show Assignment Units as (Project 2010)
Lag
Units
38. Two CRITICAL tasks vying for one resource - who wins?
Finish to Start
Task with minimum duration
d (Abbreviations Project 2010)
Resource types
39. Appears: emon means: Elapsed month
Inspect feature (Project 2010)
Lead
emo (Abbreviations Project 2010)
Table (Project 2010)
40. Project template (.mpt) - or Global MPT file. Drives what you see in the project. Corporations may have their own.
mo (Abbreviations Project 2010)
Fixed Duration
Template (Project 2010)
Views (Project 2010)
41. Create file. Set up file properties. Set a start date. Set up calendars and working time.
Do not
Table (Project 2010)
Initializing a Project (Project 2010)
Inspect feature (Project 2010)
42. Project Tab -> Change Working time. Define the actual 'hours' of work - which days work happens (weekends grayed out by default) - and 'exceptions' to standard work times. Work weeks tab present too.
Project information dialog (Project 2010)
Task with minimum duration
Network Diagram best practices
Calendar/ Working time (Project 2010)
43. Amendment to task type.
Reccuring Tasks
Effort Driven
Manual and Auto scheduled tasks
Duration
44. Finish to start - finish to finish - start to start - start to finish. All are 'at least'.
Duration
Logical Relationships in PDM
Fixed Work
Task Type
45. 'Start no earlier than' constraint.
SNET
Fixed Duration
Team Planner (Project 2010)
Accessing 'Properties' (Project 2010)
46. If '______________' isn't checked - for example - then you won't be able to set a style for critical tasks.
Calendar/ Working time (Project 2010)
Organizer (Project 2010)
Timeline (Project 2010)
Critical Tasks
47. The Precedence Diagram Method is a tool for scheduling activities in a project plan. It is a method of constructing a project schedule network diagram that uses boxes - referred to as nodes - to represent activities and connects them with arrows that
emo (Abbreviations Project 2010)
Start to Finish (SF)
Terminal element
PDM
48. File -> info -> Project information -> advanced properties.
49. Appears: emin means: Elapsed minute
Template (Project 2010)
em (Abbreviations Project 2010)
Peak
Bar Style (Project 2010)
50. Two tasks vying for one resource - who wins?
emo (Abbreviations Project 2010)
Inspect feature (Project 2010)
The task which has the LEAST slack is more important - Min-slack wins
Critical Tasks