Collaborative Development Practices Flashcards

An agile development team has adopted the practice of collective code ownership. A junior developer discovers a minor bug in a module that was originally written by a senior developer who is currently on vacation. What is the most appropriate action for the junior developer to take?

Answer: Attempt to fix the bug, write or update relevant tests, and submit the change through the team's standard review process.

Collective code ownership means the entire team is responsible for the quality of all code, not just the original author. The appropriate action is to take initiative, fix the bug, ensure it's properly tested, and follow the team's established process for code integration, which encourages shared responsibility and prevents bottlenecks.

In a pair programming session, one developer is actively writing code and focusing on the syntax and logic for the immediate task. The other developer is observing, considering the strategic direction of the code, and looking for potential errors. What is the role of the developer who is NOT typing?

Answer: The Navigator

In pair programming, the two roles are the 'Driver' and the 'Navigator'. The Driver is the one with their hands on the keyboard, writing the code. The Navigator observes, reviews the code as it's written, thinks about the overall design and strategic direction, and catches potential issues.

A team wants to improve transparency and ensure that project status, progress, and key metrics are highly visible to all team members and stakeholders at a glance. Which of the following is specifically designed for this purpose?

Answer: An Information Radiator, such as a physical Kanban board or a digital dashboard.

An Information Radiator, also known as a Big Visible Chart, is a large, physical or electronic display placed in a prominent location to show the latest information about the project. Its purpose is to make the project's status, such as work in progress on a Kanban board or progress on a burndown chart, transparent and immediately accessible to everyone, fostering communication and accountability.

Which of the following is a primary benefit of implementing Continuous Integration (CI) in an agile development environment?

Answer: It allows developers to detect integration errors early and often by merging code frequently.

The core purpose of Continuous Integration is to have developers merge their code changes into a central repository frequently. Each merge triggers an automated build and test sequence. This practice helps teams detect integration issues and bugs early in the development cycle, making them easier and less costly to fix.

A development team is struggling with knowledge silos, where critical information about certain parts of the codebase is known only by one or two developers. This has created bottlenecks and risks. Which collaborative practice directly addresses this problem by facilitating real-time knowledge transfer during development?

Answer: Pair Programming

While code reviews and collective ownership help, Pair Programming is the most direct and effective practice for real-time knowledge transfer. By having two developers work on the same task together, knowledge is shared organically, breaking down silos and cross-pollinating skills across the team.

An agile team is considering adopting Mob Programming for a particularly complex and critical feature. How does Mob Programming differ from Pair Programming?

Answer: Mob Programming involves the entire team working together on the same task, at the same time, on a single computer.

Mob Programming extends the concept of Pair Programming to the entire team. The whole team (developers, testers, product owner, etc.) gathers to work on a single task at one computer, with roles rotating. This fosters deep collaboration, immediate feedback, and rapid knowledge sharing on complex problems.