InfoQ Homepage Teamwork Content on InfoQ
-
Well Formed Teams: Helping Teams Thrive, not just Survive
What does it take to create a high-performing team? According to Doug Shimp and Samall Hazziez, a "Well Formed Team" exhibits the following characteristics: follow Agile and Lean principles, use an adaptive system with a feedback loop, are focused on the business vision, are passionate and hyper-productive.
-
Improving Productivity without Formal Metrics
Ron Jeffries has started writing a series of fictional stories based on his observation of real teams. The first story (Kate Oneal: Productivity) focuses on the character Kate O'Neal (CTO) and one of her teams "Rimshot". In this episode Ron explores achieving and measuring Productivity improvements without formal metrics.
-
Ideal Architecture is not always about Ideal Technology or Techniques
The ideal architecture is not always the one based on choices that technically would be the best. It should indeed take into account requirements of different stakeholders, which may limit the scope of choice. Phillip Calçado argues that the development team counts among these stakeholders and that constraints resulting from development environment cannot be ignored by the architect.
-
Leading Troubled Projects: Secure Your Own Oxygen Mask First
Fiona Charles' recent StickyMinds article looked at leading troubled projects. Stressing that "this is not the time for rigid process over progress," she provided valuable insights to help a team turn around a troubled project. She also reminded us to watch out for improvement: if there is none it could be a Death March, and time to leave.
-
Questioning the Retrospective Prime Directive
The 'Retrospective Prime Directive' is commonly used in retrospectives to encourage deep learning without recriminations. But what do you do when you *can't* agree that you "understand and truly believe" that everyone did their best? In this InfoQ article, a group of senior practitioners discusses the benefits and difficulties of using this practice.
-
Communicating Intent through Idiom and Paradigm Selection
What about using idioms and programming conventions as signals to achieve more readability and expressiveness? This is what Reg Braithwaite advocates for, suggesting that syntax or even paradigm choices can be a means to communicate the intent.
-
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.