4 warning signs that your team is not agile

Agile projects get the most out of people, with huge payoffs in productivity and effectiveness.

Agile projects involve close collaboration and very fast feedback loops. When it works, users' expectations are closely aligned to the project deliverables, and very little time is wasted on nice-to-haves or perfectionism that has no business impact. Agile done right is a thing of beauty, and economical to boot.

But agile productivity typically depends upon the quality of the team members. It requires high IQ, high EQ, and high focus. Put someone in with insufficient subject matter expertise, drive, or decision-making authority, and the team will be chasing its tail. Further, agile depends upon the impedance match between the resources and the tasks: if a team member just doesn't care, or can't stand to be in the room with another team member, close collaboration simply won't happen.

Since agile is all about flexibility and fast iterations, it would be a joke if you did not assess the members of the agile team as early and often as possible to detect and correct the problem children. Fail-fast on team assignments is a best practice.

If, as the Zen masters say, "how you do anything is how you do everything," it should be possible to detect team membership issues before the first sprint has completed. Ideally, you could do that before the first sprint has started. But how?

4 major areas for concern in agile teams

If there's a good thing about a character flaw, it's that the flaw's owner seldom realizes they have it...and they often have it on full display. You just have to know where to look. In most agile teams, there are four major areas for inspection/introspection: users, developers, consultants, and management. Here are forty things (in no particular order of importance) that set off red flags when we see them in agile teams.

Users who...

  • Are not engaged, interested, or motivated; are too busy with their regular jobs to participate deeply
  • Are unwilling to own problems, action items, or deadlines; are unwilling to put their name to anything (particularly requirements, validation, and test scripts)
  • View risk, change, and learning as problems, not ingredients
  • Avoid taking on action items and deadlines; allergic to follow-through
  • Display blaming behaviors and spend time on CYA activities
  • Are outspoken about what they want, but are ignorant of cloud computing realities; assume that the incremental cost of a request is zero
  • Seem to add delay and ambiguity to most decisions; hate cutting to the chase; unwilling to cut "Gordian knots"
  • Fill meetings with inconclusive chatter; tend to magnify clearly bounded issues so that they mushroom into "boil the ocean" problems
  • Are not willing to take action with incomplete information; are always trying to hedge bets
  • Have ADD or are unable to read / write anything of substance

Developers who...

  • Are unwilling to pursue rough-cut solutions
  • Suffer from perfectionism
  • Are over-focused on architecture and software longevity
  • Focus on avoiding criticism rather than getting something out there
  • Are too willing to code first and ask questions later
  • Have poor communication skills, particularly under stress
  • Detest / lack empathy for users
  • Lack project management skills or have an empty-suit manager
  • Are afraid and indecisive
  • Are unable to listen

Consultants who are...

  • Displaying bid-to-win behaviors, are desperate to win a deal or keep the account (hint to clients: interview their CTO about the bid)
  • Too flexible, too compliant, willing to make commitments they cannot really meet (hint to clients: watch out for cultural differences)
  • Unable to deliver "bad news" quickly and effectively (ditto)
  • Unable to say no and make it stick (ditto)
  • Unwilling to take charge in an uncertain situation
  • Unable to listen
  • Unable/unwilling to respond to requests the same day (hint to clients: get an SLA)
  • "Yes men" / empty suits
  • Overemphasizing speed and volume of coding, underemphasizing building the right thing
  • Unwilling to be on site (or at least in the same time zone as the rest of the team)

Management that is...

  • Unwilling to actively participate in the project, as well as champion it
  • Excessively focused on command-and-control, requiring all key decisions to be escalated; unable/unwilling to trust or truly delegate
  • More focused on budget than value; overly interested in narrowly-defined metrics; limited attention span for broad objectives
  • Exhibiting ADD or memory issues
  • Willing to promote someone who really doesn't know the domain and doesn't want to learn it
  • Rewarding fierce intramural competition, so leaders have clear incentives to low-ball budgets, over-promise deliverables, and play games with milestones
  • Holding people accountable but not giving them control of resources.
  • Using fear as a management tool, and publically punishing failure
  • Unwilling to unequivocally prioritize, set realistic deadlines, or acknowledge tradeoffs; unwilling to filter the signal from the noise
  • During contract negotiation, adds unrealistic conditions and asymmetric risk items

The bottom line

There's no scoring system here -- but if you detect enough of the issues outlined above in a team member, seriously consider replacing him/her fast. If you detect enough of the issues in the management area, it's not likely that agile is going to be a success within that part of the organization.

Join the newsletter!

Or

Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.
Show Comments

Latest Videos

Launch marketing council Episode 5: Retailer and supplier

In our fifth and final episode, we delve into the relationship between retailer and supplier and how it drives and influences launch marketing strategies and success. To do that, we’re joined by Campbell Davies, group general manager of Associated Retailers Limited, and Kristin Viccars, marketing director A/NZ, Apex Tool Group. Also featured are Five by Five Global managing director, Matt Lawton, and CMO’s Nadia Cameron.

More Videos

The best part: optimizing your site for SEO enables you to generate high traffic, and hence free B2B lead generation. This is done throug...

Sergiu Alexei

The top 6 content challenges facing B2B firms

Read more

Nowadays, when everything is being done online, it is good to know that someone is trying to make an improvement. As a company, you are o...

Marcus

10 lessons Telstra has learnt through its T22 transformation

Read more

Check out tiny twig for comfy and soft organic baby clothes.

Morgan mendoza

Binge and The Iconic launch Inactivewear clothing line

Read more

NetSuite started out as a cloud-based provider of Enterprise Resource Planning software or as NetSuite solution provider, which companies...

talalyousaf

NetSuite to acquire Bronto's digital marketing platform for US$200m

Read more

Thanks for sharing this post, its really good information I get through this blog.CDPO Online Exam Training

Infosectrain01

3 ways Booking.com is improving its B2B marketing game

Read more

Blog Posts

Getting privacy right in a first-party data world

With continued advances in marketing technology, data privacy continues to play catchup in terms of regulation, safety and use. The laws that do exist are open to interpretation and potential misuse and that has led to consumer mistrust and increasing calls for a stronger regulatory framework to protect personal information.

Furqan Wasif

Head of biddable media, Tug

​Beyond greenwashing: Why brands need to get their house in order first

Environmental, Social and (Corporate) Governance is a hot topic for brands right now. But before you start thinking about doing good, Craig Flanders says you best sort out the basics.

Craig Flanders

CEO, Spinach

​The value of collaboration: how to keep it together

Through the ages, from the fields to the factories to the office towers and now to our kitchen tables, collaboration has played a pivotal role in how we live and work. Together. We find partners, live as families, socialise in groups and work as teams. Ultimately, we rely on these collaborative structures to survive and thrive.

Rich Curtis

CEO, FutureBrand A/NZ

Sign in