The Latest

Accelerating Agile Development through Software Reuse[article]

One of the main attractions of agile methods over traditional heavyweight approaches to software engineering is their ability to accelerate the software development process. By minimizing superfluous activities and artifacts such as models and documentation and focusing developers' efforts on coding, agile methods increase productivity and reduce overall development time.

Unsolvable Conflict on Agile Teams[article]

Do you ever get the feeling that some conflict just can't be solved? The team members in conflict address the issue, it seems to go away but then it comes back. Maybe all dressed up in a new situation or with a different level of intensity, but the conflict is somehow familiar and you know that it has undoubtedly returned. If the team uses humor as a stress-reliever, you may even hear the conflict turned into a sarcastic half-joke, "OK team, just to put you on notice. Julie hates me again." Sounds almost like a marriage, doesn't it?

Lyssa Adkins's picture Lyssa Adkins
How Agile Practices Address Five Team Dysfunctions[article]

Teamwork, no matter the intentions at the start of any agile project, can be derailed by even the smallest factors. Learn how to identify the five dysfunctions of a team so that your team can address them and avoid letting them grind your production to a halt.

Tathagat Varma's picture Tathagat Varma
Software Development Screwtape Letter[article]

This is the first of many letters from Screwdisk to his protégé Virus[1]. I make no claims to the authenticity or accuracy of these letters, other than they ring true with what I have seen in the field over the last 10 years. Some of what you will read may sound a bit too familiar. It has me wondering if I have ever unknowingly been on a team with Screwdisk or Virus. I have never been able to find out who Virus and Screwdisk really are, but from what I've seen they could have been at many different organizations around the world - maybe even yours.

TechWell Contributor's picture TechWell Contributor
A Journey into Agile - Scrum Implementation at a Mature Organization - Part 2[article]

In November 2007, the organization held a global meeting on software practices. The participants were introduced to the lessons learned and best practices from a few projects in the company that had adopted a form of Agile methodology. With that exposure, the technology center in Houston set a goal to pilot one Scrum project in 2008. This article focuses on the Scrum implementation experience and the influence it has on the technology center's strategy for Scrum adoption. It is assumed that the reader is familiar with Scrum.

TechWell Contributor's picture TechWell Contributor
Group Coherence for Project Teams - Common Purpose[article]

In our continuing search for Hyper-Productivity, we have observed that a strong and highly adaptable shared sense of Common Purpose can increase the group's ability to execute on the project vision or enterprise strategy.

Agile teams apply several methods that support this. They self-organize around a common goal agreed with the customer. This goal is most often embodied in the set of stories or tasks to be included in the next iteration. A shared definition of "done," a "living" and dynamic backlog and an involved customer all help to remove ambiguity around the goal and keep each iteration adaptable to inevitable changes.

TechWell Contributor's picture TechWell Contributor
A Journey into Agile - Scrum Implementation at a Mature Organization - Part 1[article]

Midway through 2006, members of a small software development group at an engineering center for an oil field services company began having informal conversations about the nature of their work. Among other things, they pondered whether software development is an engineering discipline or a craft; and where to focus improvement efforts. These discussions sparked the interest of many on the team. They searched and came across the Agile Manifesto, which was posted in their work area. The values outlined in the manifesto appealed to the team.

TechWell Contributor's picture TechWell Contributor
Decisions, Decisions, Decisions[article]

If you're working on more than one project at a time or if your managers are asking you to do so, it's time to make some decisions. Not every project should be started or finished, and certainly no one person or team should work on all projects at the same time. The organization needs to make some decisions about whether to commit to a project, kill it so it doesn't interfere with other projects, or transform it so it can succeed in a reasonable time.

Johanna Rothman's picture Johanna Rothman
agile 2008 - Doug Bradbury - Agility, Religion, Beliefs and Practice[article]

Bob interviews Doug Bradbury about 8th Light.

Bob Payne's picture Bob Payne
Configuring CruiseControl for Continuous Integration Builds[article]

Michael Sayko introduces CruiseControl, which enables the implementing CI of Java applications. Using CruiseControl's build loop, dashboard, and build resultsJSP, Michael shows how any Java development team can receive added value through this open source tool.

Michael  Sayko's picture Michael Sayko
Are Your Pants on Fire, or Do You Suffer from Split Focus?[magazine]

Some schedule games—Split Focus and Pants on Fire—are the result of your management not making certain decisions about the project portfolio. Without those decisions, your project has problems. In this column, Johanna Rothman explains what you can do when the problems on your project are caused by your management’s lack of decision making.

Johanna Rothman's picture Johanna Rothman
The TSA and Software Quality[magazine]

As evidenced by news stories relating blatant failures on the part of the Transportation Security Administration, many organizations fail to learn much from the information testing provides. What can we do to improve the quality of our measurements so we can learn valuable lessons from the results?

Lee Copeland's picture Lee Copeland
Building a Foundation for Structured Requirements, Part 1[magazine]

Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques.

Yuri Chernak's picture Yuri Chernak
The Kanban Primer: A Cultural Evolution in Software[magazine]

Kanban,a Japanese word meaning “signal card,” introduces a new way to think about software development. Through signaling, a limit is set on work in progress resulting in a system that is never overloaded. Kanban signals do not need to be based on passing physical cards; any virtual signaling mechanism will do equally well.

David J. Anderson's picture David J. Anderson
Risk-based Testing in Action[magazine]

Risk-based testing allows project teams to focus their limited test efforts on the areas of the product that really matter, based on the likelihood of bugs in those areas and the impact of bugs should they exist. By using risk priority to sequence test cases and allocate test effort, test teams can also increase their chances of finding bugs in priority order and allow for risk-based test triage if necessary.

Rex Black's picture Rex Black


AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!