Agility and Project Leadership

And sure enough, this post by InfoWorld quotes a survey done by VersionOne on the leading cause of Agile failure:

In the survey's seventh year, "we dug a bit deeper into why agile initiatives fail and found that in two-thirds of the cases, it was either a failure to integrate the right people or to teach a team-based culture," the report states. Other reasons include communication problems between development teams and other areas of the business and problems with the Scrum master. (Scrum is a popular agile methodology, and agile itself emphasizes iterative software development, with processes evolving along the way rather than being predetermined.) External pressure to follow the traditional waterfall processes was cited as a failure factor as well.

As I've indicated in a post on Project Management Central, it's as much of a state of mind that's most important for the success of Agile and that having a self-organizing and effective team is a "state of mind" nurtured by the larger organization.

The failture to nurture this important aspect of Agile is a failure to create the culture for an organization's people to thrive.  That's why I end this post with none other than a Dilbert expose on the pitfalls of Agile adoption by the pointy haired bosses:

As part of my continuing series of posts on Agile going beyond the software development industry, I like to mention this article I ran into talking about how Agile principles were appropriated from the software development community and leveraged for marketing musicians.  As this article from Solveig Whittle states:

Of course, it didn’t take long before product managers and other marketing types realized that the same concepts which were helping their brethren across the cubicle pods over in developer-land could also be applied to the world of marketing. As a former software marketer, the idea of Agile Marketing fascinates me, as does the idea of applying it to the world of indie music marketing. This article outlines how Agile Marketing values can be used by indie musicians to guide and prioritize their online and social media marketing activities….

We struggle with finding time for both artistic creativity and promotion, we sift through unending and various advice on how to promote our music best on our websites and via social media, and we suffer insomnia as we attempt to master our social media content creation process – should we blog? YouTube? Vine? Pay for ads on Facebook or promoted posts?

The more interesting portion of the article is how the principles from the Agile Manifesto were modified to resonate with their marketing initiatives:

• Responding to change over following a plan
• Rapid iterations over Big-Bang campaigns
• Testing and data over opinions and conventions
• Numerous small experiments over a few large bets
• Individuals and interactions over target markets
• Collaboration over silos and hierarchy

As I have mention before in a discussion on the Project Management Central discussion board, that much of the success in Agile is the frame of mind one adopts rather than following some specific process or tool which goes against the very philosophy of Agile anyway.

This interesting article is another example of how transferable that mindset is.

Back in June of 2011, I wrote about the integration of Scrum with Visual Studio by installing a add on plug in to facilitate this method into your software development efforts.  Fast forward to today and you'll find that the integrations have gotten even better.

You may be a Scrum Master that is no longer as involved with the hand-on development of software, but if your leading a Windows development team your most likely going to be using Visual Studio and if your team happens to be using the latest version, it would not be a bad idea to learn about its features.

Here's a good introductory video by Richard Hundhausen for an O'Reilly press webcast that goes over all the major features:

He is also the author of the book "Professional Scrum Development with Microsoft Visual Studio 2012" that goes into more detail.

Here's a nice video from NetObjectives on a new hybrid form of test driven development called "Acceptance Test-Driven Development" (ATDD) where UAT is integrated directly with unit testing:

Unit tests are typically done to reduce technical debt, but usually at a cost of increasing development efforts.  As in everything in life, nothing is free but if executed well, the benefit to cost ratio usually weighs to the positive side when unit tests are employed correctly.

ATDD seems to offset the increase in development efforts since it allows the whole team to collaboratively discusses acceptance criteria, with examples, and then distills them into a set of concrete acceptance tests before development begins.  This ensures that everyone has the same shared understanding of what is actually being built.  It may also facilitate a better shared understanding and definition of what it means to be Done.

For those in software development doing Scrum and XP, I'd advise looking into this.

A study conducted by Yoh seems to show that companies advertised a total of 558,918 agile jobs from 2010 to 2012. During the same time period, there were merely 121,876 active candidates, just 17 candidates for every 100 jobs.  Of the available job seekers, more than 50 percent have 10 years of experience or more, while less than two percent have one to two years of experience. The agile gap exists across the U.S., varying only in its degree of severity:

• Demand outstrips supply by nearly 4x
• Companies have to pay a premium for Agile expertise
• The agile talent gap is most significant in the Pacific Northwest
• Labor pressure for agile talent goes from bad to worse
• Competition for agile talent is fierce

This is revealed in their infographic below: