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 Abel Avram on Sep 05, 2008
In this presentation filmed during Agile 2008, Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations. Some of the topics surveyed are: the adoption rate of Agile, the effectiveness of Agile approaches, the effectiveness of various techniques.
Watch: Agile in Practice: What Is Actually Going On Out There?(37 min)
Scott has conducted a series of surveys for Dr. Dobb’s Journal over the last three years on various aspects of Agile development. The results show how Agile is understood and used by people, how many are using Agile, what techniques they are using, etc.
Some of the results presented by Scott are:
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
...and somewhat cultish.
Why said like that?
Our team management is changing to Agile, is there no difference with waterfall??
Why said like that?
Our team management is changing to Agile, is there no difference with waterfall??
There is a difference. But, many organizations use Agile in waterfall way. The sad part is they don't know about it.
Can this link be fixed?
Overall, the first half of the presentation is a must-hear for anybody who is wondering why they should care about Agile/Lean.
Scott presents very interesting results of a Dr Dobbs 2008 survey:
THANKS!
PS: I completely missed the point with Modeling and TDD. Can anybody shed some light on this?
Having a look to the "Agile Project Success Rates %" slide there are 539 agile projects, which combined with the previous ones gave me a maximum of 125 companies (not hundreds by the way). I might miscalculated it, but if I am true, do you know any other report based on a higher number of surveys, please?
Cheers!
This recent news item points you to a recent, larger survey by VersionOne software. Their sample did include companies NOT using their software.
Sorry, not sure which link you mean. Please email me the url at deborah@infoq.com and I'll get it out there. Thanks!
I think Scott tried to relate or compare the concepts of Design using UML / Modeling techniques vs the generation of the Design by using Test Driven Development and Refactoring.
The basic idea in this sense is that before agile practices, the design was made by taking the requirements as input, applied some techniques and generate the design (and architecture) using models/diagrams as the main output artifact.
While if you use TDD, it comes that the design emerges as consequence of the continuous application and evolution of doing Unit Testing and Refactoring to the code you write.
Thank you Carlos. What is Scott's point regarding these practices in real life? Why oppose both techniques?
Specifying tests should not prevent people from creating some models? I agree that tests are more important than models, but models are still very often required as an aid to development, team members coordination and maintenance...
I guess I will have to listen to that part again... :-)
Olivier,
I believe the point Scott was making is that since the majority of professing agilists don't do TDD then TDD is not a good practice and the converse is true for modeling.
The person in audience questioned the validity of the survey because the majority of respondents do detailed documentation. In my opinion, that is a good question and Scott didn't answer it to my satisfaction.
Maybe Scott's point is that the agile practices that are not adopted by the masses should be cut?
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.
11 comments
Watch Thread Reply