Industry Watch: Going agile isn't so agile
September 15, 2011 —
(Page 1 of 2)
Converting your development team, and perhaps even your entire organization, to agile practices involves something completely counter-intuitive: detailed, structured planning.
Most people think of that old Nike slogan when they decide to adopt agile practices: “Just do it.” Yet it’s that very idea that often leads to poor communication, frustration over a lack of wide buy-in, and, ultimately, failure of adoption.
“People misunderstand the depth and breadth of change required for transformation” to agile practices, said Tamara Sulaiman Runyon, a certified Scrum trainer and Project Management Professional at CollabNet. She has created something she calls the Agile Transformation Competency Framework to help organizations not merely “do” agile, but successfully transform their culture from awareness of agile to assimilation of those practices.
Before organizations decide to transform themselves into agile businesses, they must first define why they are doing it, based on measurable and observable metrics such as increased profitability or higher market share, she explained. “Agile for agile’s sake is not enough,” she said. “The reasons for transformation must be clear.”
Once the rationale is laid out, the framework advises that the organization establishes a baseline for where it is now: Are there pilot projects running? Have multiple teams adopted some agile practices? Interviewing team members will give the organization an idea of where to focus time and money to move along to transformation, said Sulaiman Runyon.
Her framework is meant to keep the road map to transformation visual and adaptable, in a way that is easy to evangelize throughout the organization. It is not, she said, a prescription for making the switch.
The next stage involves individuals exploring practices, perhaps launching a pilot team or two. There is little budget for training, no true collaborative process, and information remains in silos. These are what Sulaiman Runyon calls the awareness and willingness stages of adoption.
Next, business-value drivers are introduced as executive sponsorship begins. In-house expertise evolves, there is more training and coaching, and the small change to agile begins to ripple into other areas as the organization gets product management and senior management aligned with the new agile values. At this point, tools are selected, agile engineering practices are institutionalized, metrics are standardized, and reporting up to management is optimized. This is the adoption stage where the application of agile practices is put into place.
Related Search Term(s): agile
Share this link: http://sdt.bz/35944
Most Read Latest News Blog Resources
Achievements and learning: Gamification comes to businesses and schools
Startup takes page from gamers by offering achievement marks to get developers more engaged in their projects
|
|
Zeichick’s Take: The handheld and the tablet, circa 1976
Texas Instruments' and Hewlett-Packard's calculators were doing things decades ago we take for granted today
|
|
Google talks tools at AnDevCon III
New 3D debugging tool and recent ADK changes are detailed by Google developers at the third Android Developer Conference
|
|
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
Achievements and learning: Gamification comes to businesses and schools
Startup takes page from gamers by offering achievement marks to get developers more engaged in their projects
|
|
Google talks tools at AnDevCon III
New 3D debugging tool and recent ADK changes are detailed by Google developers at the third Android Developer Conference
|
|
SmartBear rolls out new quality solution: API Complete
Software gives organizations ability to write test scripts and monitor APIs by bridging the DevOps divide
|
|
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
Creation
To write better software, cultivate your ability to be creative.
|
|
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
|
|
How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
|
|
Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
|
Five SCM Best Practices
Two-thirds of all software projects fail, according to the Standish Group’s CHAOS study. Improper usage of software configuration management...
|
|
|
Best Practices for Branching and Merging Patterns
Development teams often create a branching pattern, usually drawn out on a white board or in a Visio document, that is used as a model to...
|
|
Automated Error Reporting
We invite you to read a short e-zine that tells you all about automated error reporting for .NET applications. This 8-page e-zine is packed...
|
|
The End of Application Redeploys
Imagine that every time you wanted to write, send or receive an email, you needed to restart your computer. How much time would this take, a...
|