Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Deborah Hartmann on Oct 26, 2006 06:49 AM
VersionOne Software, an Atlanta-based provider of enterprise project and lifecycle management solutions for agile development, this autumn conducted a global survey to highlight the value teams deliver using Agile software development. The result is their "State of Agile Development" Survey Results, co-sponsored by The Agile Alliance. The survey indicates that the key reasons people are adopting Agile are: managing changing requirements and priorities, and accelerating time-to-market.

"[the responses to similar questions] 2 or 3 years ago would primarily would have been from small teams - we've seen an uptake in the size of teams adopting or considering adopting Agile... roughly a third of responses were from organizations of 250 or more. [size of software organization]."Holler suspects that we're not yet nearing the end of this increase in adoption:
I think any time you're talking about a fundamental change in the way people do business, we're talking at least a double-digit time frame, at least ten years. ...maybe five years ago it was primarily developer-led, and then two or three years ago, team-led, now we're seeing a lot of management- and project-management-led, and I think the future is going to be executive-led.In fact, this survey seems to show that, in contrast to the early years of the Agile movement, Agile methods are now almost as likely to be championed by a member of senior management as by grass roots leaders like team leads and architects:
What role most closely identifies the initial champion of Agile development within your organization?The full results of the survey are available online, as well as in a .pdf download, on the VersionOne site.
28% VP / Director of Development 18% Project Manager 13% Team Lead 11% President / CEO 7% Architect 5% CIO 5% Consultant
Give-away eBook – Confessions of an IT Manager
Ebook: Scaling Agile with C/ALM
The Agile Business Analyst: Skills and Techniques needed for Agile
There's a question I don't see anyone asking on surveys yet: How many have "unadopted" Agile? This might be difficult to ask on a survey - it's a retrospective-style question which is best asked in an open-ended manner: "What didn't work?" However, information about teams that either throw out Agile wholesale, tweak it beyond recognition, or no longer want to use the term Agile could be interesting, if we want to learn about what's happening with adoption. deb
Deb, That's an interesting thought. Maybe the questions should try and highlight how much teams value agile principles. For example, one question may be "Does your whole team sit together?" This might identify how teams value communication. Another question might be "How often do you deploy working software". This might identify how teams value delivery working software as opposed to documention. These questions might invoke an honest answer which would then give a deeper insight as to how agile teams really are. Warren
Lets try that again. Deb, That's an interesting thought. Maybe the questions should try and highlight how much teams value agile principles. For example, one question may be "Does your whole team sit together?". This might identify how teams value communication. Another question might be, "How often do you deploy working software?". This might identify how teams value delivering working software as opposed to documentation. These questions might invoke an honest answer which would then give a deeper insight as to how agile teams really are. Warren
I would love to hear suggestions such as this for questions. I'm going to repeat my agile adoption survey in the new year and definitely intend to rework the questions. It will make comparisons difficult but I hope to get better quality data. It's really hard to design a good survey, and an evolutionary approach is a good strategy in the long run. - Scott Practice Leader Agile Development, IBM Methods Group
Note: there's further conversation on this subject at the ScrumDev list http://groups.yahoo.com/group/scrumdevelopment/message/16925
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
5 comments
Watch Thread Reply