Agile Software Development Explained: A Beginner’s Guide

A team of software developers at Mountain Goat Software recently employed a technique called “Roman Voting” to quickly reach consensus on a set of proposed improvements, a practice gaining traction within agile development teams.

Agile software development, a methodology focused on iterative progress and collaboration, frequently utilizes retrospective meetings to assess completed work and identify areas for enhancement. A core component of these retrospectives is surfacing and prioritizing those improvements, often through voting mechanisms. Retrospective voting, as a general practice, allows team members to express their opinions on what worked well and what needs adjustment, with the results informing action plans for future “sprints” – short, time-boxed periods of development.

While several voting methods exist, “dot voting” is a common approach where participants are given a limited number of “dots” to place next to the items they prioritize. Yet, the simplicity of Roman Voting – a simultaneous thumbs-up for agreement and thumbs-down for disagreement – is proving popular for its speed, and clarity. According to Applied Frameworks, a consultancy specializing in agile practices, the technique streamlines decision-making and fosters team collaboration.

The Roman Voting technique, as described by Applied Frameworks, involves all participants voting simultaneously. A thumbs-up signifies “yes” or agreement, while a thumbs-down indicates “no” or disagreement. The proposal passes or fails based on a pre-determined rule, typically consensus or majority rule. The technique’s proponents emphasize maintaining a “clean” approach, avoiding variations like sideways thumbs that could introduce ambiguity.

The demand for structured consensus-building techniques arises from potential challenges within retrospective voting. ProjectManagers.net notes that team members may be influenced by personal interests, subjective preferences, or a desire to maintain the status quo. Facilitators, such as Scrum Masters or product owners, often need to guide teams toward agreement on objectives or improvements. Techniques like dot voting, or Roman Voting, are tools to achieve this.

Beyond specific voting methods, broader consensus-building approaches include facilitating discussions and seeking agreement on significant objectives, as a product owner might do with stakeholders, or on improvements to be pursued by a development team following a retrospective. Mike Cohn, an agile consultant and author, highlights the importance of these techniques for high-performance teams.

A recent discussion on Reddit’s r/softwaredevelopment forum indicates that “confidence votes” are also used by some teams, though the specifics of that method were not detailed in the available information. The increasing focus on team consensus reflects a broader trend within software development toward collaborative and iterative processes.