A systems development methodology refers to a structured approach used in software development and systems engineering to guide the design, development, and implementation of software applications.
* Why Option A (Waterfall) is Correct:
* Waterfall methodology is a linear and sequential systems development methodology where each phase (e.g., requirements, design, implementation, testing, deployment) must be completed before moving to the next.
* It is widely established and historically one of the first software development methodologies.
* Used in large-scale enterprise projects where detailed planning and structured execution are required.
* Why Other Options Are Incorrect:
* Option B (PRINCE2 - Projects in Controlled Environments):
* Incorrect because PRINCE2 is a project management framework, not a systems development methodology.
* Option C (ITIL - Information Technology Infrastructure Library):
* Incorrect because ITIL is a set of IT service management (ITSM) best practices, not a software development methodology.
* Option D (COBIT - Control Objectives for Information and Related Technologies):
* Incorrect because COBIT is a governance framework for IT management and controls, not a development methodology.
* IIA GTAG - "Auditing IT Projects and Systems Development": Highlights Waterfall as a traditional systems development methodology.
* IIA's Global Technology Audit Guide on IT Risks: Discusses software development lifecycle risks, including Waterfall methodology.
* COBIT Framework - BAI03 (Manage Solutions Identification and Build): References structured methodologies like Waterfall in IT governance.
IIA References:

* Definition of Project Crashing:
* Project crashing is a schedule compression technique used in project management to reduce the project completion time without changing its scope.
* It involves adding extra resources (labor, equipment, budget) to critical path activities to complete them faster.
* Key Aspects of Project Crashing:
* Reduces project duration by increasing resources.
* Leads to higher costs due to additional labor or expedited material procurement.
* Used when project deadlines must be met and standard scheduling techniques are insufficient.
* Why Other Options Are Incorrect:
* A. It leads to an increase in risk and often results in rework:
* While crashing can increase costs and risk, it does not necessarily result in rework unless poorly executed.
* B. It is an optimization technique where activities are performed in parallel rather than sequentially:
* This describes fast-tracking, not crashing. Fast-tracking involves overlapping tasks, while crashing adds resources to speed up tasks.
* C. It involves a revaluation of project requirements and/or scope:
* Crashing does not change project scope; it only shortens the schedule by allocating additional resources.
* IIA's Perspective on Project Risk and Management:
* IIA Standard 2110 - Governance emphasizes the importance of project risk assessment, including schedule compression risks.
* COSO ERM Framework identifies project cost overruns and resource misallocations as key risks in project execution.
* PMBOK (Project Management Body of Knowledge) defines crashing as a schedule compression technique used when deadlines must be met at additional cost.
IIA References:
* IIA Standard 2110 - Governance & Risk Oversight in Project Management
* COSO Enterprise Risk Management (ERM) - Project Risk Considerations
* PMBOK Guide - Schedule Compression Techniques (Crashing & Fast-Tracking) Thus, the correct and verified answer is D. It is a compression technique in which resources are added so the project is completed faster.

The personnel director should tailor the discussion to the listener by describing how the employee's department evaluates performance and what is expected of him/her. The director should also obtain feedback from the employee to determine if everything is clearly understood.