← All CIS Flashcard Decks

Implementation Methodologies Flashcards

7 cards from real CIS practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Implementation Methodologies flashcards as text
  1. What is the key difference between configuration and customization in a platform implementation?

    Answer: Configuration uses the platform's built-in tools; customization involves modifying core code

    Configuration leverages native platform capabilities (forms, workflows, rules) without touching core code, while customization modifies or extends the platform's underlying code.

  2. In the Waterfall implementation methodology, which phase directly precedes the Testing phase?

    Answer: Development

    In Waterfall, the sequence is Requirements → Design → Development → Testing → Deployment, so Development precedes Testing.

  3. What is a 'runbook' in the context of a go-live implementation plan?

    Answer: A step-by-step operational guide for executing deployment tasks

    A runbook documents every task, command, and verification step needed to execute the deployment, enabling teams to follow a consistent go-live process.

  4. Which technique is used to identify the longest sequence of dependent tasks that determines a project's minimum duration?

    Answer: Critical Path Method (CPM)

    The Critical Path Method identifies the longest chain of dependent tasks, revealing the shortest possible project duration and tasks with zero float.

  5. During data migration in an implementation project, what does 'data cleansing' involve?

    Answer: Detecting and correcting inaccurate, duplicate, or incomplete records

    Data cleansing identifies and fixes errors, duplicates, and incomplete records in the source data before migrating them into the new system.

  6. What is the purpose of a RACI matrix in an implementation project?

    Answer: Defining team members' roles and responsibilities for each task

    A RACI matrix clarifies who is Responsible, Accountable, Consulted, and Informed for each project task, reducing ambiguity and communication gaps.

  7. In an ITSM implementation, what is the 'change freeze' period?

    Answer: A time window before go-live where no changes are made to stabilize the environment

    A change freeze is a defined period—typically before and immediately after go-live—during which no new changes are permitted, ensuring system stability.