Practice Test Geeks(CAD) Certified Agile Developer Practice Test
← All CAD Flashcard Decks

Collaborative Development Practices Flashcards

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

Read the first 7 Collaborative Development Practices flashcards as text

  1. What is 'promiscuous pairing' in Agile collaborative development?

    Answer: Pairing with a different partner every few hours to maximize knowledge spread

    Promiscuous pairing deliberately rotates partners frequently throughout the day to maximize knowledge distribution across the team.

  2. Which scenario BEST demonstrates psychological safety in a collaborative Agile team?

    Answer: A junior developer openly flags a design flaw in a senior's code without fear of retaliation

    Psychological safety exists when anyone can raise concerns regardless of seniority without fear of punishment or ridicule.

  3. An Agile team's daily standup consistently runs 30 minutes. What collaborative improvement should they try first?

    Answer: Enforce a strict 3-question format and timebox each speaker to 2 minutes

    Introducing a strict 3-question structure and individual timeboxes focuses standups and is the simplest fix before more drastic changes.

  4. Why is 'whole team quality' a core principle of collaborative Agile development?

    Answer: It distributes responsibility for quality across all roles, not just testers

    Whole team quality means everyone — developers, testers, BAs — shares ownership of the product's quality outcome.

  5. A team wants to reduce the 'hero developer' anti-pattern where one person saves every sprint. What practice helps most?

    Answer: Cross-train team members and cap individual contributions through pairing and rotation

    Cross-training and pairing spread capability so no single developer becomes the indispensable rescuer every sprint.

  6. Which tool category MOST supports asynchronous collaboration on distributed Agile teams?

    Answer: Persistent documentation and decision-log tools like wikis and ADRs

    Wikis and Architecture Decision Records (ADRs) allow distributed teams to collaborate across time zones without requiring simultaneous availability.

  7. In Agile collaborative development, what is the recommended approach when two developers disagree on a technical solution?

    Answer: Timebox a spike to compare the approaches empirically, then decide together

    A timeboxed spike produces evidence rather than opinion, enabling the team to make a data-driven collaborative decision.