teams

Articles

Using Your Tools Always Read the Label: Getting the Most from Your Tools

It is possible to find a new, innovative use for a tool, but it’s much more likely that you’ll do better using the tool in the way its creators intended. And whenever you reach for a tool, check that it’s actually going to help solve the challenge you’re facing. This article explains why first and foremost, conversation is more important than a shiny new tool.

Seb Rose's picture Seb Rose
Traceable Tests Guide Your Agile Development with Traceable Tests

Testing professionals who are learning about agile often want to know how they can provide traceability among automated tests, features, and bugs and report on their testing progress. Here, Lisa Crispin gives an example of how her previous team worked together to integrate testing with coding and helped everyone see testing progress at a glance.

Lisa Crispin's picture Lisa Crispin
Indispensable Employee Management Myth 36: You Have an Indispensable Employee

An employee may become indispensable through arrogance or happenstance. These employees can cause bottlenecks and often prevent others, as well as themselves, from learning and growing professionally. "Firing" these indispensable employees sets your team free to work even when the expert is not available.

Johanna Rothman's picture Johanna Rothman
the Season for Annual Planning 'Tis the Season for Annual Planning: How to Have a Jollier Experience This Year

One of the primary goals of annual planning is to translate aspirational strategic plans into realistic execution plans. Sadly, rather than delivering plans we can all feel good about and believe in, too often it leaves us depressed about the work ahead of us. This article shares five practical principles to remove the emotions associated with annual planning.

Catherine Connor's picture Catherine Connor
Agile Values Five Common Pitfalls When Organizations Neglect Agile Values

As agile development has erupted over the software landscape, its core philosophy often has been neglected as organizations hurry to implement cherry-picked practices in the name of pragmatism. By avoiding these five common pitfalls, companies can better realize the true benefits of agile: high productivity, great software quality, and happy customers.

Victor Szalvay's picture Victor Szalvay
Friendly Competition Management Myth 35: Friendly Competition Is Constructive

Competition between teams does not improve performance. In fact, the added stress may shift team members' focus from creating a quality product to self-preservation due to fear of failure. Johanna suggests managers emphasize collaboration between teams over competition.

Johanna Rothman's picture Johanna Rothman
Agile Planning The Five Levels of Agile Planning

Contrary to popular belief, agile projects require as much planning as any other project type. It is the timing of this planning and how we attempt to minimize wasted effort that is different from other approaches. This article attempts to explain the different levels of agile planning and how we utilize them in an ongoing project.

Paul Ellarby's picture Paul Ellarby
Value and Innovation Team Assembly and Its Impact on Value and Innovation

Simply putting a handful of developers together and calling it a “team” doesn’t cut it. There’s a better, more analytical approach to team assembly that results in more cohesive teams, faster ramp-up times to peak velocity, and improved innovation, business outcomes, and value.

Michael Rosenbaum's picture Michael Rosenbaum
Technical Practices Accelerating the Adoption of Technical Practices

Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.

Scott Barnes's picture Scott Barnes Clifford Berg
Jumpstart Team Efforts Why Teams Stop Improving—and How to Jumpstart Their Efforts

One of the most important features in agile software development is continuous improvement. However, after an initial burst of inspiration and productivity, teams may stop improving because they believe there are no issues left to address or the issues are too difficult to solve. People need to switch their mental models to keep addressing processes efficiently.

Aleksander Brancewicz's picture Aleksander Brancewicz

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.