Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Project Management 101

Status
Not open for further replies.

Cheater123

Technical User
Jul 21, 2015
1
US
1. Any change in a project is a.....
a. Scope Creep
2. Noticing and Interpreting non-verbal behavior is one example of a non-measurable competency
a. True
3. What does the Conditions of Satisfaction document ultimately deliver?
a. The POS (Project Overview Statement)
4. One way to not classify a project is….
a. By the people involved
5. Can the Project Manager expect 100% work effort each day?
a. False
6. Too much deviation in near critical path activities could change the critical path.
a. True
7. Which is the riskiest project to accomplish?
a. Type A
8. Assumptions are an important part of the POS.
a. True
9. Which causes the project manager and team less pain during a project?
a. Good Planning
10. Dependencies should never involve…
a. Personality constraints
11. Conversations and negotiations can lead to a document called the Conditions of Satisfaction.
a. True
12. When building a project schedule….
a. You create a Gannt chart
13. Team leaders have no responsibility for any part of the project
a. False
14. A project is a sequence of unique, complex, and connected activities having one goal
a. True
15. A project manager can arbitrarily change the task dependencies
a. False
16. When creating the WBS, one rule(s) to use is…
a. Answers A & B
17. Scope the project, develop detailed plan, launch the plan, and monitor/control project progress; are the only steps involved in the TPM life cycle
a. False
18. Planning
a. None of the above
19. The MAIN purpose of the POS is for team guidance
a. False
20. Micro management is the only way to keep the best employees
a. False
21. You can only produce a WBS thru the Top-Down Approach
a. False
22. An essential skill for a project manager is
a. Listening
23. Is it REQUIRED to include Assumptions, Risks & Obstacles in the POS
a. False
24. Quality management is not part of, nor important to true project management
a. False
25. A program is a collection of
a. Projects
26. The POS (Project Overview Statement) , PDS (Project Definition Statement) & Conditions of Satisfaction are static documents.
a. False
27. Activity A must be complete before activity B can begin
a. Finish to Start
28. Projects usually do not have a specific time-line, budget or specification to follow
a. False
29. Design-Build-Test-Implement is a common Verb-type approach to the WBS for systems development
a. True
30. Executing
a. Launches the Plan
31. What is one document we can use to manage client expectations?
a. The Conditions of Satisfaction
32. Risk analysis assesses factors, probability and potential damage for a project
a. True
33. When construction companies build roads they never use a management reserve because
a. Not enough information to be really answer the question
34. One of the first tasks for a project manager is to _____ the work
a. Define
35. Any change in a project not originally planned is
a. Scope Creep
36. Why would you write a POS when you inherit a project
a. To understand the Project
37. A team members has gotten behind schedule, but is still reporting to be on schedule; this is called
a. Hope Creep
38. When the team member arbitrarily adds functions to the delivery
a. Feature Creep
39. How many goals can a project have?
a. One
40. When estimating activity duration the project manager will use only one method
a. False
 
Cheater123, is there a question here? You posted this as a question.

==================================
adaptive uber info galaxies (bigger, better, faster, and more adept than agile big data clouds)


 
The whole posting is kinda "creepy", as creep is an answer in at least 4 of the questions, and the answer is always a). [wink]

Actually, I disagree with several of the answers, starting with #1. A change in a project *might* be scope creep, but it might be a change in budget, staffing, or even a legitimate change in requirements, aka "scope change".

==================================
adaptive uber info galaxies (bigger, better, faster, and more adept than agile big data clouds)


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top