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. Can be added to the ribbon - and it walks user through formatting of the gantt chart. Pretty cool.






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






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






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






5. Create file. Set up file properties. Set a start date. Set up calendars and working time.






6. Tables are made up of fields.






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






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






9. Appears: eday means: Elapsed day






10. Appears: ewk means: Elapsed week






11. Changing the working time in the 'details' section of the working time dialog won't change the default start time in the options -> scheduling settings. Try to keep these in sync.


12. Task calendar - resource calendar - base calendar.






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






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






15. Tasks - resources - assignments - all have dialogs. Example: resource leveling. Project information dialog very important.






16. Network Diagrom -> Format ribbon -> format.






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






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






19. .mpp file extension. The actual project file.






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






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






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






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






24. Appears: emon means: Elapsed month






25. ______ link Summary Tasks.






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






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






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






29. Appears: emin means: Elapsed minute






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






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






32. Gantt Chart with 'Entry' table on left.






33. If '______________' isn't checked - for example - then you won't be able to set a style for critical tasks.






34. Matches the outline number initially in Project 2010. It is common for work breakdown structure elements to be numbered sequentially to reveal the hierarchical structure. For example 1.3.2 Rear Wheel identifies this item as a Level 3 WBS element - si






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






36. Appears: day means: day






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






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


39. Appears: wk means: week






40. 'Start no earlier than' constraint.






41. Appears: hr means: hour






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






43. The WBS contains 100% of the work defined by the project scope and captures all deliverables - internal - external - interim - in terms of the work to be completed - including project management.


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






45. Single Start - Single Finish. No 'danglers'. Everything must be connected. No loops.






46. The acceloration of the successor task. 'Negative lag'






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






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






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






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