New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Chris Sims on Jul 02, 2008
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.
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
SCM best practices for multiple processes, releases & distributed teams
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply