<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team on Scholion</title><link>https://scholion.thluiz.com/tags/team/</link><description>Recent content in Team on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 06 Oct 2026 04:20:06 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/team/index.xml" rel="self" type="application/rss+xml"/><item><title>Consensus-Driven Development</title><link>https://scholion.thluiz.com/notes/consensus-driven-development/</link><pubDate>Thu, 16 Apr 2015 17:54:47 -0300</pubDate><guid>https://scholion.thluiz.com/notes/consensus-driven-development/</guid><description>The article argues that software teams should use consensus, not majority voting, to make decisions. It outlines ways to build agreement, handle dissent, and know when a group decision is appropriate.</description></item></channel></rss>