Test your basic knowledge |

CAPM Time Management

Instructions:
  • Answer 31 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. Computer simulation that throws a high number of "what if" scenarios at the project schedule to determine probable results.






2. Float.






3. A technique primarily made up of two means of compressing the schedule: crashing and fast-tracking.






4. Method of diagramming project activities to show sequence and dependencies.






5. Probable number of periods this activity should take with the probable range of results (1 week +/- 3 days)






6. How much time an activity can be delayed without affecting the project's finish date.






7. A schedule buffer used to reduce schedule risk.






8. A form of expert judgment often used early on when there is little information available. It is performed from the top down - focusing on the big picture.






9. Means of gathering expert judgment where the participants do not know who the others are and therefore are not able to influence each other's opinion. Designed to prevent "groupthink."






10. A technique to show scheduling possibilities where early and late start and finish dates are calculated for every activity without looking at resource estimates.






11. Activities with finish to start relationships cannot start until their predecessors have been finished; however - if you have 5 days of lead time on an activity - it may begin 5 days before its predecessor.






12. High-level points in the schedule used to track and report progress.






13. A type of network diagram where the boxes are activities - and the arrows are used to show dependencies between the activities.






14. Method of estimated where experts are asked to provide input to the schedule.






15. Activities that must be completed before other activities either start or finish (mandatory - discretionary - and external).






16. Delay between an activity and the subsequent one dependent upon it.






17. The path through the network diagram that show which activities - if delayed - will affect the project finish date.






18. A situation that occurs when an activity's start date comes before a preceding activity's finish date.






19. Applying more resources; increases cost






20. Rules for which no formula exists; usually derived through trial and error.






21. Perform activities in parallel that normally are done in sequence; increases risk






22. Method for calculating late start and late finish dates for an activity.






23. Final result is an activity list (similar to Scope Decomposition where the result is a WBS)






24. A rarely used type of network diagram where activities are represented by arrows connecting the nodes.






25. An activity in a network diagram that does not have any time associated with it. Only included to show relationship and is usually dotted or dashed line.






26. Comparing planned versus actual schedule dates.






27. List of every activity that will be performed on the project.






28. A type of network diagram where activities are represented on rectangular nodes with arrows representing the dependencies.






29. Or free slack--how much time an activity can be delayed without affecting the early start date of subsequent dependent activities.






30. The method for calculating early start and early finish dates for an activity.






31. The approved schedule that is used as a basis for measuring and reporting. It includes the original project schedule plus all approved updates.