Test your basic knowledge |

Project Management Using Microsoft Project

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. Tasks - resources - assignments - all have dialogs. Example: resource leveling. Project information dialog very important.






2. 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.






3. 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.






4. Shows closest thing to a 'resource gantt chart'. Shows tasks by resource. Also shows unassigned tasks - and unscheduled tasks. Allows for user-controlled scheduling.






5. 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.






6. Finish to start - finish to finish - start to start - start to finish. All are 'at least'.






7. Appears: emin means: Elapsed minute






8. The number of resources required to get the tasks/assignments completed.






9. Work divided by available resource units. Formula: D=W/U






10. 1. Initiation 2. Planning 3. Execution 4. Monitoring & Control 5. Closing






11. Contains information relative to tasks.






12. Work - resource - cost.






13. An approach for monitoring project progress that relies on the budgeted cost of activities completed to ascribe value






14. Function key 5. You can go directly to ID - or 'date'.






15. Always preserve the number of people working on a task. Changing units when fixed will impact duration.






16. U = W / D Work divided by duration.






17. Appears: min means: minute






18. Appears: day means: day






19. Project template (.mpt) - or Global MPT file. Drives what you see in the project. Corporations may have their own.






20. Appears: mon means: month






21. 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






22. .mpp file extension. The actual project file.






23. Gantt Chart -> Format -> Bar Styles segment -> format drop down. Adjust all aspects of the bars in the gantt.






24. Ensuring that the successor activity does not begin until after the predecessor activity is completed is implementing a start-to-finish (SF) model. This is the most logical path to follow when planning a project. Those in project management should be






25. Always preserve the duration of a task. Changing duration when fixed will impact work.






26. Two tasks vying for one resource - who wins?






27. Amendment to task type.






28. The total direct and indirect costs incurred in accomplishing work on an activity during a given period.






29. To switch between ____________: (Project 2010) - Use the bottom-left icon. Use the ribbon. Task mode column in entry table. File -> options -> schedule.






30. Tables are made up of fields.






31. Hiding does not delete data. If you hide a column - data maintains - but to get it back - you'll need to right click - insert column.


32. Appears: ehr means: Elapsed hour






33. Task ribbon -> 'task' -> recurring task. An easy way to schedule reccuring meetings.






34. File -> Options -> Quick Access tool bar. Examples: Tables and Vies - good stuff.


35. W = D + U Duration plus available resource units






36. 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.






37. File -> Options -> Scheduling --> Drop down for Decimal or Percentage.






38. Can be added to the ribbon - and it walks user through formatting of the gantt chart. Pretty cool.






39. Appears: ewk means: Elapsed week






40. Shows logical relationship between tasks. View tab -> 'split view' section -> details checked -> More views -> Select there.






41. 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






42. File -> Info -> Organizer. Access global mpt - delete views - etc. (ADD MORE)






43. A terminal element is the lowest element (activity or deliverable) in a WBS; it is not further subdivided. Sometimes called a 'work package' - but NOT synonymous.






44. Focus on Gantt -> Format ribbon ->






45. 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






46. Vitally important. It shows how much time remains - which indicates whether or not tasks need to be re-planned.






47. Two critical tasks - both same duration - vying for one resource - who wins?






48. 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.






49. View -> Timeline check box. Shows timeline - but by default - nothing's on it. To add items - right click and 'add to timeline'.






50. Their purpose is to ORGANIZE. Summary tasks have work packages or other summary tasks which comprise the parent summary task. Summary tasks are NOT scheduled. The children tasks are what need to be scheduled.