A normal and healthy situation in a team of peers is open communication. This is precisely what is expected in an agile team:
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Communication: Everyone is part of the team and we communicate face to face daily. We will work together on everything from requirements to code. We will create the best solution to our problem that we can together.
Recently, a known technical fellow posted his current opinion about what he recognizes as test-driven design. This is good, very good. This way we help ourselves and feed up the dialogue and discussion.
If agile and adaptive thinking mean something, then such meaning also includes the notion of feedback loops. That is the act of checking current state of affairs against a reference or desired output, where the measured output and measured error can be contrasted and upon which further adjustments can be based.
If such meaning is also granted to the words agile and adaptive thinking, then discussion and debate are useful mechanisms to apply as concrete manifestations of those words.
In that sense, I certainly see a blog entry which questions or challenges ideas as a very fortunate one. In fact, precisely that –the questioning and going deeper in meanings– is what any community needs if they want to stay away from the negative effects of groupthinking.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
In fact, members of an agile team, as reflective practitioners, usually make plans to improve on the same intellectual patterns of philosophical inquire. For more of this: What is agile development?, and also: My Technical Readiness