You call that Agile?
Monday, January 29th, 2007Many companies are throwing around the term agile when defining who they are and what they can offer but, as the Agile In Action blog points out, many may not be practicing what they preach.
In this post I have collected some of the telltale signs for use when determining if a company is truly agile:
“Notice the characteristics of communications with the company. One of the things I notice are the amount of red-tape involved in setting up any meetings. The more paperwork the worse it is likely to be. Long company email signatures can be the first clue.
Companies with dress down Friday who display a large cardboard cut-out of what garments constitute casual wear want drones and probably don’t encourage new ideas. Motivational posters decking the walls could be a hint that the management team is clueless.
Companies with very swish offices tend not to understand the need for developer messy thinking tools such as whiteboards. Conversly, companies whose offices look in a poor state of repair are probably also neglecting their computing infrastructure so developers will have a hard time setting up development environments, etc.
A clue that teams may be open to new ideas can be books (fiction or technical) and newspapers around. Personalised team environments can hint that the team are trusted and allowed to make changes in their space. Seeing developers talking to each other around a whiteboard or screen rather than with headphones on can also hint that they are open to reviewing ideas with their peers.”
“It‘s difficult to characterize an entire organisation as ‘Agile’ without working with them for a while either as a partner or as a member of staff - you need to assemble some tacit knowledge about that companies’ culture and decision making process.
It‘s much easier to analyze a specific product development team as you can look at their environment, team identity, output etc. There are a couple of properties one can extrapolate from such a team to it‘s surrounding company - is the team empowered to perform its function? is there respect between the team and the company? does the team have a clear project charter and product owner? You can get a pretty good feel for what the company is like from these kind of indicators.
It‘s also good to look at the relationship the company has with its partners and suppliers - do they enter into mutual benefit partnerships and work proactively with suppliers to improve both companies’ positions? Essentially you’re trying to determine how much trust exists in these relationships - it‘s not the only indicator but it is a useful one - it allures to the underlying culture of an organisation.
Structurally I would expect an Agile organisation to be ‘wide and not deep’; management hierarchy and bureaucracy is kept to a minimum with workers being aligned along product streams rather than into functional hierarchies such as ‘technology’ and ‘hr’.”

