Fast Bytecodes for Funny Languages
Cliff Click discusses how to optimize generated bytecode for running on the JVM. Click analyzes and reports on several JVM languages and shows several places where they could increase performance.
- Java,
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
Agile Projects: Five Ways to Fail When You Scale
Webcast: Applying lean thinking to the governance of software development
Agile Development: A Manager’s Roadmap for Success
The Agile Business Analyst: Skills and Techniques needed for Agile
Lean Software Development Governance, a whitepaper by Per Kroll and Scott Ambler
VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
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
groups.yahoo.com/group/scrumdevelopment/message...
Cliff Click discusses how to optimize generated bytecode for running on the JVM. Click analyzes and reports on several JVM languages and shows several places where they could increase performance.
Scott Ambler, Practice Lead for Agile Development at IBM, speaks on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.
Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD).
Smooks is best known for its transformation capabilities, but in this article Tom Fennelly describes how you can also use it for structured event streaming.
Successful architectures evolve over time to meet changing business requirements. Luke Hohmann presents how to collaborate with key members of your business to manage architectural changes.
In this article, Dr. Tobias Komischke explains how colors used in a GUI can influence our interaction with a computer and offers advice on using the appropriate colors for the interface.
In his presentation, recorded at QCon San Francisco, MuleSource architect Dan Diephouse explores ways to use the Atom Publishing Protocol (AtomPub) when building services in a RESTful way.
Grzegorz Gogolowicz and Matthew Dressel demonstrate how to extend Windows SharePoint Services 3.0 to support column level permissions.
5 comments
Reply