TL;DR: How to Identify an Agile Organization
How to identify an agile organization is — given the market-entry of the late majority to agile development practices – nowadays more important than ever: No matter how large the pay cheque, life is just too short to spend it on unfulfilling projects!
I can support your quest as an agile practitioner for the next suitable employer or client with this article, covering the three different phases of gathering information on the agile maturity level of an organization.
The job market for Scrum Masters is hot
This recent study — “LinkedIn Data Reveals the Most Promising Jobs of 2017” — listed ‘Scrum Master’ to be one of the most promising jobs of 2017:
10. Scrum Master
Median Base Salary: $100,000
Job Openings (YoY Growth): 400+ (104%)
Career Advancement Score (out of 10): 8.0
Top Skills: Agile Methodologies, Software Project Management, Scrum, Requirements Analysis, SQL
Noting that SQL is listed as a skill prerequisite, I am not sure whether the author understands the required skill set completely.
That aside, however, the reported rise in the number of available positions year on year (104 per cent) reflects the exponential growth in the demand for Scrum Masters and Agile Coaches.
The reasons for this are apparent, with software eating the world, and the pace of innovation accelerating as the market-entry barriers of the technology sector are continuously lowered. Venture capital is also widely available, and startups are gaining more of an innovative advantage over established organizations. Current tech trends as analyzed in “Deloitte’s Tech Trends 2017 Report” are threatening the very existence of a lot of legacy organizations.
Turning this legacy ship around and taking on this wave of innovative competition bow-first is a difficult thing to do for an organization founded in the golden age of Taylorism [‘Principles of Scientific Management’ propounded by F.W. Taylor in 1911.]. With its structure of functional silos and command and control management style, transforming into a learning organization takes time, because the organizational debt, acquired over decades, results in a latency that justifies the ship/tanker metaphor in this case.
The long established practice of legacy organizations countering this effect was to outsource innovation by acquiring promising startups. The problem with this is that the valuation of such startups has skyrocketed in recent years, while the financial prowess of legacy organizations has diminished (in many cases) at the same time. The decade-long window of opportunity in outsourcing disruptive innovation is closing.
Apart from striking the colors and admitting defeat, the only alternative is to change the legacy organization itself by transforming into a learning organization. With the ensuing difficulty, however, of refocusing everyone on creating hypotheses, running experiments, and embracing failure, while abandoning the command and control management style at the same time, legacy organizations have tended to give autonomy, accountability, and transparency a try at team level — mostly within the product delivery organization in charge of creating software.
The rise of agile practices such as Scrum can quite likely be attributed to the fact that the large consultancies (formerly die-hard proponents of Taylorism and command and control structures) are now offering professional services based on agile practices. (See, for example: “McKinsey’s Digital Labs”.)
Ultimately, whatever the motivation, most organizations acknowledge by now that the old way of innovating products is no longer viable — at least not in the software sector. With the desire to be agile, or at least develop software in an agile way, we now observe the huge demand for Scrum Masters and Agile Coaches — with most of this demand fueled by recent converts. In “Crossing the Chasm” terms, Agile has become mainstream; the late majority is starting to adopt Agile. [ Moore, Geoffrey A. “Crossing the Chasm”, 3RD Ed. New York: HarperCollins, 2014. Print.]
Therefore, looking for a new job or client, we Scrum Masters and Agile Coaches need to answer two questions of ourselves:
- Do I want to work for a nascent agile organization (of the late majority) where my work will likely be met with resistance at multiple levels?
- If I don’t want to work for a nascent agile organization, how do I identify an organization which established agile practices that are compatible with my mindset?
The two questions are relevant both to applying to available positions, as well as identifying suitable employer or clients for a proactive application.
Read More: “Is the company right for me?”
📕 Now Available: ‘How to Get Hired as a Scrum Master’
Scrum Master Career: How to Get Hired as a Scrum Master: From Job Ads to Your Trial Day — Learn How to Pick the Right Employer or Client details how Scrum Masters and Agile Coaches can systematically identify suitable employers or clients to avoid mismatches and disappointments at a later stage. If you are planning a career move into the Scrum Master profession, don’t miss out on these tips.
Scrum Master Career: How to Get Hired as a Scrum Master is currently available as a Kindle ebook. Shortly, the paperback version will be available, too.
How to Get an Idea of an Organization’s Agile Maturity
It is impossible to assess the agile maturity of an organization solely from the outside.
However, it is possible to acquire enough of an understanding of the organization’s agile practices that would foster asking the right questions at a later stage, for example during an initial job interview. Or, it may be concluded early in the assessment process (see below) that the organization is not compatible with the personal expectations of an employer or client — which is acceptable by saving wasted time and effort for all involved. Consider the popular saying: There is no project interesting enough that you just couldn’t walk away from it.
The good news is that all organizations that truly embrace agile practices are usually openly talking about their journeys (unless they need to honor compliance rules), and are transparent and actively supporting the agile community. The reason for this support is simple: Being transparent and supportive is the best way to pitch the organization (and its agile culture) to prospective new team members —and the war for talent is even more imminent for agile practitioners.
The necessity of critical information is the basis for all research activity during the three distinct phases of the assessment process:
- Proactive research
- Job advertisement
- Job interview
Phase 1: Proactive Research
Source 1: An opportunistic search via Google
As a first step, always search the organization’s name in combination with a variety of agile-related keywords, such as:
- Scrum Master
- Product Owner
- Continuous integration
- Continuous delivery
- Design thinking
- Lean startup
The purpose of this exercise is to discover an organization’s use of agile practices and the associated maturity level, by answering these questions:
- Scrum, Kanban, XP, Lean UX, Design Thinking — What are they practicing?
- Are the current Scrum Masters or agile coaches working at the organization?
- How many engineers or engineering teams are working for the organization?
- What is the size ratio between the product management and engineering teams?
- Is the organization practicing continuous product discovery?
- Is the organization practicing DevOps?
The initial search results will provide a first impression, directing further searches of blog posts, videos of conferences or local meetups, slide decks, podcasts, or threads in communities. A truly agile organization will leave traces of a large variety of content.
The mere quantity of results, though, does not signal that the organization in question has already passed the test, so to speak. There is no way to avoid checking the content. Here’s an example:
InfoQ — community news site for spread of software innovation and knowledge — has a rigorous editorial process and focuses on delivering quality content to its audience. Contrary to InfoQ’s standards there are quite a few articles on Scrum Alliance, for example, that could raise eyebrows for scrutiny. These articles are often celebrating one form or another of cargo cult practices within an organization which could be masquerading as agile, but is certainly not agile.
A good rule of thumb when scanning search results is noting the diversity of sources. If you find content only on the company blog, and it has barely been shared or commented upon, it might hint that the content manager is either not understanding the job, or that the content is not relevant enough to be of interest within the agile community.
Advanced Tips: Use BuzzSumo to analyze a specific article or keyword for its popularity in social share counts. In addition, search for the title of the content piece on Twitter and have a look at the search results: who from the agile community is sharing this content?
Source 2: Ask peers for help via Reddit, Hacker News, Slack & LinkedIn
The archive of HN is of particular interest. It is not just because of the sheer number of available articles or threads there, but also the partly heated discussions going on in the comments. Be aware, though, that ‘agile’ as a concept is challenged by a lot of the outspoken community members (namely, independent developers) both on Reddit and HN.
Beyond passively scanning the archives, posting a direct question to peers is an alternative. HN is likely a waste of time, and if using Reddit – choose the Subreddits /agile and /scrum for a possibly better outcome.
You can probably expect more support by asking the members of the ‘Hands-on Agile’ Slack community for help. This is a world-wide community of Scrum Masters, agile coaches, and Product Owners that has proven to be very supportive.
Note: You can sign-up for free here.
There are also LinkedIn groups available which focus on agile practices — some with more than 100,000 members. (For example, Scrum Alliance has a group on LinkedIn that seems more active than its own online community.) After having joined them, post your question(s), remembering to be compliant with the group rules. Expect your first posts to be moderated, though.
Some recommended LinkedIn groups are:
- Agile Project Management
- Agile DevOps Networking Group
- Lean Agile Software Development Community
- Agile Coaching
- Scrum Practitioners & Scrum Masters
- Lean Agile Software Development Community
If posting a question to a LinkedIn group, expect to monitor it carefully and interact with answering members in a timely manner: not interacting with responding group members may be considered rude and possibly lead to being banned from posting in the group again.
Read More: Etiquette in technology
Lastly, try Quora, directing a question to Quora members active in the agile realm as to whether the organization of interest has an agile mindset.
Note: In doing so, avoid asking anonymous questions — which tend to have a significantly lower answering rate.
Source 3: Is the organization sponsoring or organizing Meetups, Barcamps, or Conferences?
Supporting public events is the highest form of contribution to the agile community by an organization.
There are four different levels of engagement:
- Organizing conferences (or Barcamps)
- Sponsoring conferences in cash
- Providing speakers to conferences,
- Sponsoring local Meetups and Barcamps by providing a venue (with crisps and beer!)
If an organization provides this level of support to the agile community, the talk about this will certainly be on the company blog, the engineering blog, or in a press release in their public relations section.
In the unlikely case that any reference cannot be found, just contact the Public Relations department who will provide the required information.
Browsing conference sites for sponsors
Conference sites are a good ground for identifying prospective organizations when considering to proactively apply for a Scrum Master position. Check carefully for two things: sponsors and speakers.
Search for sponsors that are practicing agile in their daily operations. Usually, a larger sponsor package will include a speaking slot at the conference.
Attending such a session will provide direct access to the speaker and thus a first contact in the inner circle of that organization’s agile practitioners. This tends to be valuable: HR departments often rely on the private networks of the organization’s available agile practitioners to identify suitable candidates for job openings as Scrum Master or Agile Coach. (Accordingly, attending local Meetups can also be a worthwhile investment for job seekers.)
Note: A consultancy offers agile coaching and training jobs, so unless that type of employment is desired it might be desirable to ignore sessions provided by companies like agile42.
These are the usual suspects looking for new clients or consultants among the attendees.
Browsing conference sites for speakers
Personally, a more promising approach, by comparison, is to search for non-professional speakers who are aligned with an organization that is not sponsoring the conference. These speakers may indicate a suitable, prospective employer or client after already having gone through the selection process for speaking proposals and vetting of their contribution for originality.
The same approach can apply to contributions at Barcamps, although a disadvantage is that the critical information is only available during an event. While the speaker list of a conference is available in advance to stimulate ticket sales, it is the nature of a Barcamp that the schedule, and hence the speaker list, is available only on the day of the Barcamp. If already planning to attend a Barcamp, it may just be an inconvenience and not a concern. Timing is crucial, though, so please keep in mind that tickets for Barcamps are often sold out within minutes. (For example, the 400+ tickets for the UX Camp Berlin 2016 were gone in less than two minutes.)
There are numerous conferences regarding agile practices, so here are just some of the listings:
- Agile 2017
- Agile Testing Days
- Agile on the Beach
- QCon New York
- Business Agility 2017
- LeanKanban Conferences
For an additional listing of agile conferences, check TechBeacon’s list for 2017.
Lastly, the big conferences are often considered must-attend events — useful to earn Scrum Alliance SEUs or improve professional visibility within the agile industry. Alternatively, smaller conferences often prove to be more effective by providing information that helps identify a suitable, prospective agile organization. The larger the conference, the more possibility of noise camouflaging that information.
Browsing Meetup.com for organizers
Meetup.com is a great site to discover which events of the agile community are happening locally and who is organizing them.
There are thousands of Meetups around the world, t covering the topics of agile frameworks and practices, software engineering, and product development in general.
Metaphorically, the low-hanging fruit is, of course, an organization that leaves a footprint in the agile community by organizing its own events. A good example of this category is Berlin-based “Zalando”.
Back in 2015, Zalando [Europe’s largest online fashion retailer.] introduced its version of Agile, dubbed ‘radical agility’. It has since proven to be a smashing success, not just fueling the bottom line of the business, but also the company’s ambition to build an outstanding product delivery organization.
A quote from its Senior Manager of Corporate Communications:
Over the last year and a half, we have doubled the technology team from around 800 in 2015 to over 1,600 currently. In addition to changing our business model, we also implemented a unique culture within the technology team called Radical Agility: This has seen monthly technology applications grow from 500 to over 2,000, and allows us to ensure that we are hiring only the best quality.
Zalando is hosting several events relating to best engineering practices, as well as (generally radical) agility-related events, every month on their own campus. If you want to work in an agile manner in Berlin, Zalando is certainly an organization worth considering.
Besides spotting the Zalandos of this world, the other benefit of analyzing a local event is identifying the independent organizers in the community. Most often, these are peers dedicated to the agile cause who are giving back to the community. Given their extended networks, they are usually highly knowledgeable regarding the agile maturity level of local organizations, and may know other peers that might be supportive of a quest. Reaching out to them by attending their normally free events is, therefore, a good strategy for gathering information.
Stay tuned — Part 2 will cover how to analyze job advertisements, and how to prepare for the job interview.
Subscribe to Our “Food For Thought” Weekly Newsletter and Follow Us on Twitter
If you like to receive a curation of the best posts on agile and lean methodologies, and product management every Sunday, subscribe to our hand-curated newsletter „Food for Agile Thought“
—and follow Age of Product on Twitter.