Transactions without Transactions
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Aug 17, 2008
In this presentation filmed during Agile 2008, Ron Jeffries and Chet Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense in the software development world.
Watch: Natural Laws of Software Development (1h 30 min.)
Ron and Chet say that, usually, in business, nothing goes according to the plan, but in all other businesses, except software development, they know before hand they are not going to meet the deadline, and proceed accordingly. We need to provide the same ability to have predictability. It is not possible to have predictability if one is given all the specifications and attempts to complete an entire project before a deadline is met because nobody knows for sure how much of the project has been done. Instead, if the project is approached step by step by doing chucks of it, one could figure out if the project is in graphic or not.
Ron and Chet continue by saying that if we deliver Running Tested Features, then the business management can have predictability, early releases, and will request high value features first, which in end will be a return of investment. Businesses need incremental software development: "if they have it, they can manage it, make more money with it, understand what's going on with it."
Defects may be accounted as negative features. Not knowing what they are means not knowing for certain where we are in the development process. An important cause of defects is misunderstanding the requirements, which happens easily when a team has to deal with all of them at once, instead of incrementally receiving and addressing them. Requirements are well understood during conversations person to person. User stories come handy because they open the conversation which conducts to confirmation. The end result is clarity, the clear understanding of requirements.
In that manner, Ron and Chet derive in their presentation all Agile practices as inherent effects of the natural laws of software development.
Transforming Software Delivery: An IBM Rational Case Study
Agility at scale, become as agile as you can be
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!
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.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
3 comments
Watch Thread Reply