InfoQ Homepage Teamwork Content on InfoQ
-
Review Board - Online Code Review Tool
Recently there has been a resurgence in interest in code reviews. InfoQ looks at Review Board, an open source application that helps facilitate the code review process, that has been gathering momentum in the open source community.
-
Responsibility, Personal Agility, and Other Touchy-Feely Ideas
Successful Agile teams are predominantly characterized by their culture and not their practices. This sentiment rings true to many (if not most) in the Agile field. Christopher Avery, who has made his name in the world of organizational transformations, has taken his work on Responsibility and focused it directly on Agile practices. Is Personal Agility the key to successful Agile adoption?
-
Measure Teams, Not Individuals
Michael Dubakov recently expressed warning against the measurement of individual velocity and individual estimate accuracy. His view: measurement of these metrics not only provides no more useful information than is already available with their team-level equivalents, but may also have a tendency to encourage teams into behaviors that reduce effectiveness.
-
Why Crunch Mode Doesn't Work
Evan Robinson recently posted an article on why the practice of 'crunch time' doesn't work. Despite a century of studies showing that long-term output is maximized near a five-day, 40-hour work week, projects still hit the crunch usually to the detriment of the team. InfoQ looks at why crunch time is still so prevalent in the software industry and, if we know it's bad, why do we still do it?.
-
I'm Not Sure What You Heard is What I Thought I Said
Are family celebrations a challenge? You get together to catch up and swap stories, and invariably something gets "taken the wrong way." It's not restricted to families is it? So it's not surprising that the Satir Communication Model jumped the fence from family therapy to team building! J.B. Rainsberger uses an amusing Christmas-at-Walmart anecdote to illustrate its use.
-
Debate: Scaling teams up in productivity rather than in personnel
Larger team size prevents from adopting the whole range of language abstraction tools and puts constraints on productivity. Reg Braithwaite believes that tools should not be tuned to the size of the team. He advocates for building teams around the tools and keeping them small. It appears however that team growth is often inevitable. What can be done then to maintain quality and productivity?
-
No More Self-Organizing Teams?
Jim Highsmith has suggested that the term self-organizing team "has outlived its usefulness in the agile community and needs to be replaced". He suggests that Light-Touch Leadership is more appropriate. But does this negate the need for self-organizing teams and the focus on individual team members "doing what it takes" to get things done?
-
Leadership is not Obsolete for Self-Organizing Teams!
In this talk, software thought leader Mary Poppendieck reviewed 20th century management theories, including Toyota and Deming, and went on to talk about "the matrix problem", alignment, waste cutting, planning, standards and other topics including the role of measurement: "cash flow thinking" over "balance sheet thinking". InfoQ presents video of this popular talk from the Agile2007 conference.
-
Ready! Set! Getting New Team Members off to a Good Start.
How long does it take a newcomer to become an effective member of your team? Learning is integral to agile methodologies, but the learning needs of the newcomer are different from established team members: in a standup meeting, "I did (unintelligible) yesterday" offers them more questions than answers. Pat Kua suggests some practices that specifically reduce the "setup time" for new team members.
-
How Long Should Retrospectives Last?
The original definition of a retrospective, as presented by Norm Kerth, was a 3 day, offsite meeting. In, Agile Retrospectives, we are given 5 phases to be covered, but no specific guidance on time. In her recent article, Rachel Davies suggests that we have 30 minutes per week under review. How long should a retrospective last to be effective?
-
InfoQ Presentation: Jean Tabaka on Surviving Meeting Burnout
Teams moving to an Agile approach may feel irritated as they move from command-and-control to a collaborative culture - which can start to look like non-stop meetings, starting first thing every Monday morning. In this InfoQ exclusive presentation, recorded at Agile2007, Agile coach Jean Tabaka shared her experiences working with teams, offering guidance on how to alleviate meeting burnout.
-
Microsoft announces MSDN Tester Center
Today Microsoft launched a new site on MSDN focused on the testing community and tester professionals at large. The site is meant to promote testing within the greater Microsoft developer ecosystem.
-
Presentation: Implementing Scrum In A Distributed Software Development Organization
At Agile2007 we heard the tale of a distributed Scrum project with 50 people in 4 continents. BMC Identity Management decided to build their next generation product, including architectural changes and component integration, using Scrum to handle the uncertainty of their product's requirements. This presentation talks about how.
-
Peter Hosey of Adium on Code Reviews
There is no question that formal code reviews catch bugs and can delay the inevitable "big ball of mud" that all successful projects seem to turn into. However, arranging a meeting for every check-in quickly becomes untenable on all but the most critical of projects. Peter Hosey talks about his experiences and how he conducts code reviews in Adium.
-
Ted Neward's thoughts on Architecture Roles & Responsibilites
Ted Neward shares his thoughts on the roles and responsibilities of the Software Architect, discussing what an architect does, how to approach the role, and if architects are still relevant.