Concurrency: Past and Present
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Tracking change and innovation in the enterprise software development community
Posted by Chris Sims on Jul 02, 2008 05:31 AM
VersionOne, a maker of agile project management tools, has announced that the third annual 'State of Agile Development' survey is open for participation. The online survey is intended to gauge the value of agile development practices in the field. Results will be announced on August 4th, at the Agile 2008 conference in Toronto.This year's survey takes about 10 minutes to complete and will be open until July 21. Participants may remain anonymous, or may choose to provide an email address so that VersionOne can email them the results.
The survey covers:
The first survey , in 2006, had 722 participants from 47 countries. Of the companies represented, 84% were using agile somewhere in the organization. On average, participants had been using agile methods for 2.3 years.
When asked to identify the role of the initial champion of agile development, the results were:
| VP / Director of Development | 28% | |
| Project Manager | 18% | |
| Team Lead | 13% | |
| President / CEO | 11% | |
| Architect | 7% | |
| CIO | 5% | |
| Consultant | 5% |
The full results of the 2006 survey [pdf] are available for download.
Last year nearly 1,700 people from 71 countries participated in the second survey. Of the companies represented, 73.2% were using agile somewhere in the organization.
Asked how long they had been practicing agile development, respondents said:
| Greater than 5 years | 12% | |
| 2 - 5 years | 26.1% | |
| 1 - 2 years | 20.9% | |
| 6 - 12 months | 16.6% | |
| Less than 6 months | 16% | |
| Never | 8.4% |
And what role as the initial champion of agile development?
| Team Lead / Dev. Manager | 22% | |
| VP / Director of Development | 19% | |
| C-Level Executive | 18% | |
| Project Manager | 15% | |
| Architect | 8% | |
| Developer | 6% |
The full results of the 2007 survey [pdf] are available for download.
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
The End of Middleware: Freedom from IT Stacks as we know it
Six Free Project Management Certification Training Courses
Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
No comments
Reply