Project documentation and archival MCQs – Software Project Management
1. What is the primary purpose of project documentation in software project management?
a) To increase project duration
b) To ensure all project activities are recorded and can be referred to later
c) To hire new team members
d) To test software
Answer: b) To ensure all project activities are recorded and can be referred to later
2. Which of the following documents is typically created first in a software project?
a) Project Closure Report
b) Requirements Specification Document
c) Post-Project Review
d) Risk Management Report
Answer: b) Requirements Specification Document
3. A “Project Charter” is important because it:
a) Defines the project’s purpose, objectives, and stakeholders
b) Details the testing methods for the software
c) Describes user interface design
d) Lists all the project bugs
Answer: a) Defines the project’s purpose, objectives, and stakeholders
4. The process of archiving project documentation ensures that:
a) Documentation is kept for future reference
b) The project is restarted
c) Code is updated
d) The project team disbands
Answer: a) Documentation is kept for future reference
5. Which document serves as the main source of truth for project requirements?
a) Design Document
b) Requirements Specification Document
c) Test Plan
d) User Manual
Answer: b) Requirements Specification Document
6. What is the purpose of a project plan in software development?
a) To estimate the budget
b) To outline tasks, timelines, and deliverables
c) To identify bugs
d) To design the UI
Answer: b) To outline tasks, timelines, and deliverables
7. Which of the following is NOT a key component of a Software Project Plan?
a) Schedule
b) Budget
c) Hardware specifications
d) Risk management strategy
Answer: c) Hardware specifications
8. What should be done with lessons learned documentation after a project is completed?
a) It should be archived and shared with future project teams
b) It should be discarded after project closure
c) It should be used only for audit purposes
d) It should be ignored
Answer: a) It should be archived and shared with future project teams
9. A project closure report typically includes:
a) Future project budgets
b) A summary of project deliverables, performance, and lessons learned
c) Code changes made during the project
d) Employee evaluation forms
Answer: b) A summary of project deliverables, performance, and lessons learned
10. What is the primary function of a “Change Log” in project documentation?
a) To track modifications in project timelines
b) To record changes in project scope, schedule, or costs
c) To assess team performance
d) To list software bugs
Answer: b) To record changes in project scope, schedule, or costs
11. Archiving project documentation helps in:
a) Reusing successful practices in future projects
b) Extending the project timeline
c) Changing project scope
d) Evaluating team salaries
Answer: a) Reusing successful practices in future projects
12. Which document outlines the tasks and timeframes for project activities?
a) User Manual
b) Project Schedule
c) Risk Report
d) Quality Plan
Answer: b) Project Schedule
13. What is a “Risk Register” used for?
a) Documenting the project’s risks and their mitigation strategies
b) Tracking project expenses
c) Documenting system specifications
d) Recording project deliverables
Answer: a) Documenting the project’s risks and their mitigation strategies
14. A configuration management plan is primarily concerned with:
a) Managing changes to project documents and software code
b) Budgeting for hardware
c) Planning testing phases
d) Scheduling meetings
Answer: a) Managing changes to project documents and software code
15. The project documentation that details how software will be tested is known as:
a) Test Plan
b) Design Document
c) Project Scope Statement
d) Change Log
Answer: a) Test Plan
16. Project archival ensures:
a) Historical project data is preserved for future use
b) The project can be restarted at any time
c) Code changes can be applied easily
d) The project team is dissolved
Answer: a) Historical project data is preserved for future use
17. Which document outlines the acceptable quality standards for project deliverables?
a) Quality Management Plan
b) Test Plan
c) Requirements Document
d) Risk Management Plan
Answer: a) Quality Management Plan
18. What is the main objective of a project audit document?
a) To examine the project’s success against its initial objectives
b) To hire new project managers
c) To assess the system’s UI design
d) To identify software bugs
Answer: a) To examine the project’s success against its initial objectives
19. Who is responsible for approving changes documented in the change log?
a) Project Manager
b) Development Team
c) Change Control Board
d) Test Lead
Answer: c) Change Control Board
20. The project initiation document primarily contains:
a) The project’s objectives, scope, and stakeholders
b) The project’s testing strategy
c) A list of software bugs
d) A timeline for system maintenance
Answer: a) The project’s objectives, scope, and stakeholders
21. Which document tracks the project’s actual costs versus budgeted costs?
a) Financial Management Plan
b) Cost Baseline Report
c) Change Log
d) Quality Plan
Answer: b) Cost Baseline Report
22. A software project archive typically includes:
a) All final versions of project deliverables, plans, and reports
b) Only the project schedule
c) Draft versions of code
d) Employee payroll details
Answer: a) All final versions of project deliverables, plans, and reports
23. The “Project Scope Statement” is essential for:
a) Defining the work required and the boundaries of the project
b) Managing risk
c) Listing test cases
d) Recording time sheets
Answer: a) Defining the work required and the boundaries of the project
24. What is the purpose of a “Stakeholder Register” in project documentation?
a) To track all stakeholders, their roles, and their communication preferences
b) To list user requirements
c) To track project bugs
d) To schedule software releases
Answer: a) To track all stakeholders, their roles, and their communication preferences
25. Which document outlines the corrective actions taken to resolve project issues?
a) Issue Log
b) Risk Register
c) Quality Plan
d) Project Charter
Answer: a) Issue Log
26. The document that defines the exit criteria for the project is the:
a) Project Closure Report
b) Test Plan
c) Change Log
d) Risk Management Plan
Answer: a) Project Closure Report
27. What type of document is a “User Acceptance Test (UAT) Plan”?
a) A document detailing how the system will be accepted by the end-users
b) A list of changes in software code
c) A budgetary document
d) A report on software architecture
Answer: a) A document detailing how the system will be accepted by the end-users
28. Which document provides a high-level overview of project status for executives?
a) Project Status Report
b) Code Review Document
c) Stakeholder Register
d) Test Plan
Answer: a) Project Status Report
29. Why is project documentation important in Agile projects?
a) It helps maintain a record of iterations and decisions made
b) It is not used in Agile projects
c) It only tracks software bugs
d) It helps in creating marketing campaigns
Answer: a) It helps maintain a record of iterations and decisions made
30. A post-implementation review is conducted to:
a) Analyze the project’s success and identify areas for improvement
b) List future projects
c) Evaluate the salaries of team members
d) Develop a new product
Answer: a) Analyze the project’s success and identify areas for improvement
31. Which document specifies the acceptance criteria for deliverables?
a) Requirements Specification Document
b) Quality Management Plan
c) Acceptance Criteria Document
d) Stakeholder Register
Answer: c) Acceptance Criteria Document
32. A project communication plan includes details on:
a) Who needs to be informed about project updates and how often
b) Coding languages to be used
c) Testing methods
d) Project expenses
Answer: a) Who needs to be informed about project updates and how often
33. The lessons learned document is typically reviewed during:
a) Post-project evaluation
b) Software coding
c) Initial project kickoff
d) Risk assessment
Answer: a) Post-project evaluation
34. Project documentation related to the software architecture is called:
a) Architecture Design Document
b) User Manual
c) Test Plan
d) Project Charter
Answer: a) Architecture Design Document
35. Which of the following is NOT part of project archival?
a) Storing project deliverables
b) Evaluating the current project team
c) Recording lessons learned
d) Archiving project plans
Answer: b) Evaluating the current project team
36. What type of document is typically used to track project bugs and defects?
a) Issue Log
b) Risk Register
c) Financial Management Plan
d) Project Schedule
Answer: a) Issue Log
37. What does a “Risk Mitigation Plan” describe?
a) The steps to reduce or eliminate project risks
b) The project budget
c) The user interface design
d) The project’s marketing strategy
Answer: a) The steps to reduce or eliminate project risks
38. The scope of a project is detailed in which document?
a) Project Scope Statement
b) Test Plan
c) Risk Management Plan
d) Quality Assurance Plan
Answer: a) Project Scope Statement
39. What does a “Quality Management Plan” focus on?
a) Ensuring that project deliverables meet the required standards
b) Specifying the coding language
c) Identifying project risks
d) Defining project goals
Answer: a) Ensuring that project deliverables meet the required standards
40. What type of document is a “Work Breakdown Structure (WBS)”?
a) A visual representation of project tasks and sub-tasks
b) A list of project stakeholders
c) A timeline for project deliverables
d) A description of project risks
Answer: a) A visual representation of project tasks and sub-tasks
41. A document detailing the functionality and limitations of the system is called:
a) System Specification Document
b) Test Plan
c) Code Review
d) Risk Log
Answer: a) System Specification Document
42. What is the purpose of an “Issue Log”?
a) To document and track project-related issues and their resolutions
b) To track software bugs
c) To schedule project meetings
d) To define project goals
Answer: a) To document and track project-related issues and their resolutions
43. Which of the following is an essential part of the project’s final documentation?
a) A summary of completed tasks and outcomes
b) Future project goals
c) A list of potential risks
d) A marketing plan
Answer: a) A summary of completed tasks and outcomes
44. What does a “Change Control Plan” address?
a) How to manage changes in project scope, budget, and schedule
b) How to finalize project requirements
c) How to evaluate team performance
d) How to assign project tasks
Answer: a) How to manage changes in project scope, budget, and schedule
45. A “Resource Allocation Plan” specifies:
a) The resources required for project activities and their allocation
b) The project’s goals and objectives
c) The testing methods used in the project
d) The timeline for deliverables
Answer: a) The resources required for project activities and their allocation
46. The “Project Status Report” is used to:
a) Track the project’s progress and provide updates to stakeholders
b) Design the system’s user interface
c) Identify project risks
d) Evaluate team members
Answer: a) Track the project’s progress and provide updates to stakeholders
47. In project documentation, the “Acceptance Test Report” details:
a) How the software is tested and validated against requirements
b) The project’s budget
c) Future software updates
d) Code changes made during the project
Answer: a) How the software is tested and validated against requirements
48. What is documented in a “Post-Project Review”?
a) The outcomes of the project and lessons learned for future improvements
b) The software design
c) A list of team salaries
d) The coding methods used in the project
Answer: a) The outcomes of the project and lessons learned for future improvements
49. The “Communication Management Plan” outlines:
a) How communication will be handled throughout the project
b) The project’s coding standards
c) Project testing procedures
d) The project timeline
Answer: a) How communication will be handled throughout the project
50. The “Project Procurement Plan” details:
a) How goods and services will be acquired for the project
b) How software will be tested
c) How the project team will be selected
d) The budget for project tools
Answer: a) How goods and services will be acquired for the project