Enabling and Sustaining High Performing Teams

by Shane Hastie on  Nov 06, 2011

Agile practices should foster high-performance self-organizing teams. It is important that high-performance equals value delivery, to ensure that the team solves the right problem. It is also important to create an environment where high-performance can flourish which requires thinking and action at a management level. We examine three commentators perspectives on enabling high performance.

Is Velocity Killing Agile?

by Michael Floyd on  Nov 04, 2011 1

Velocity, the measure of work completed by the team divided by the time taken to complete it, is increasingly being used to manage the productivity of a team and as a comparison between teams. Jim Highsmith, Mark Levison, and Scott Ambler discuss the misuse of velocity as a productivity measure.

Simple Tools Preferred in the Agile Tools Space

by Vikas Hazrati on  Sep 07, 2010 2

Agile does not necessarily mandate or recommend the use of tools. Ideally the development could be done on a command line interface with requirements present on index cards. However, in the last few years, several tools have emerged and they have acted as a catalyst to successful Agile development. Migan and Gaia recently conducted a survey to find out the use of such tools in the Agile space.

The “Do Not Disturb” Team Member

by Vikas Hazrati on  Mar 09, 2010 41

Many developers like to work in isolation, for some time, if not always. XP recommends a room arrangement called “Caves and Commons”. Commons area is organized to maximise osmotic communication. Caves are meant to facilitate isolation for activities like personal email, phone calls or a quick spike. However, there could be a situations where a team member wants to take this isolation too far.

What Really Motivates Workers

by Shane Hastie on  Feb 05, 2010 5

In a recent Harvard Business Review article Teresa M. Amabile and Steven J Kramer challenged the commonly held mnagement belief that Recognition is the most motivating and positive factor in the workplace. Their multi-year study tracked the motivation and emotions of hundreds of knowledge workers and identified POGRESS as the single most important factor for individual motivation in the workplace

Need an Answer to Context Switching? Get Disturbed

by Vikas Hazrati on  Sep 15, 2009 2

Context Switching is defined as changing focus and attention from one task to the other in relatively short periods of time. It is widely considered harmful for the team member and the project that he is working on. Charles Miller mentioned a few ways of how they handle context switching at Atlassian.

Agile Addresses "The Five Dysfunctions of a Team"

by Deborah Hartmann Preuss on  Aug 06, 2009 1

Tathagat Varma, general manager with a large provider of IT management solutions, wondered whether Agile's productivity improvements could be linked to how it improves teamwork. His article analyses Agile values and practices by mapping them against Patrick Lencioni's business fable "The Five Dysfunctions of a Team."

Kent Beck Suggests Skipping Testing for Very Short Term Projects

by Mark Levison on  Jun 18, 2009 10

Kent Beck suggests that on very short term projects, when you're trying to figure out if there is a viable concept, you might do less (even no) automated testing to help get off the ground quickly. This goes against all of the conventional wisdom surrounding TDD.

How TDD and Pairing Increase Production

by Mike Bria on  May 27, 2009 7

"Test-driven Development" and "Pair Programming" are two of the most widely known of agile practices, yet are still largely not being practiced by many agile teams. Often, people will cite being "too busy" to adopt such practices as TDD and pairing; in essence, implying that striving for high code quality will reduce productivity. Mike Hill explains how this logic is seriously flawed.

Is Five the Optimal Team Size?

by Vikas Hazrati on  Apr 14, 2009 18

There have been a lot of discussions and debates about the optimal team size for maximum productivity. While most Agilists agree that smaller teams are more functional and productive as compared to larger teams, however defining the optimal team size is still a challenge.

J.B. Rainsberger: "Integration Tests Are A Scam"

by Mike Bria on  Apr 09, 2009 18

Well-known agilist and TDD expert J.B. Rainsberger has begun a series of posts to explain why his experience has led him to the thought-provoking conclusion that "integration tests are a scam".

Focus Improvement on Bottleneck Constraints

by Chris Sims on  Mar 30, 2009 5

In My Framework is More Productive than Your Framework, Ken DeLong examines approaches to making software projects more productive. He finds that despite the hype about frameworks, languages, and project management tools, these tend not to be the bottlenecks. Ken believes that the largest productivity gains are likely to come from improved communication, code readability, and debugability.

Keep Focus By Tuning Out Your Computer

by Mike Bria on  Feb 25, 2009 3

Agile practitioners have come to understand the negative effect “context-switching” has on productivity when it comes to your projects and teams. To what degree do the same ideas apply at the daily task and personal interaction level, and what can people do to avoid micro-level multi-tasking problems? Phil Gerbyshak offers some advice.

"Good Design" Means ...?

by Mike Bria on  Jan 29, 2009 9

It's not news that at the heart of successful software systems (and, frankly, fulfilling software careers) is good design. Also not news is that defining what "good design" really means has been at the heart of many debates, papers, talks, books, discussions, and more for ages. To help, J.B. Rainsberger and Scott Bellware offer some advice to follow until that one true definition comes along.

Measure Agile Productivity in $

by Jon Arild Tørresdal on  Jan 26, 2009 2

Earlier Scott Ambler posted an article of how to measure productivity on agile teams by utilizing acceleration. Recently he followed up with another post where he answers some frequently asked questions related to agile productivity and acceleration. Specifically one question answers how to measure the amount of $ saved by an accelerating team.

General Feedback
Editorial and all content copyright © 2006-2014 C4Media Inc. hosted at Contegix, the best ISP we've ever worked with.
Privacy policy