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 Aug 01, 2008
In this interview made by Deborah Hartmann of InfoQ, JeanTabaka talks about team collaboration as a key ingredient of the Agile development, but she also mentions RAPID management as a solution for the product owners who found themselves in an Agile environment.
Watch: Jean Tabaka About Team Collaboration and RAPID Management (25 minutes).
During her consulting work aimed to help companies becoming Agile, Jean has discovered there are teams who do not want to become self organized, they don't want to make decisions, to take tasks or to make their own estimates. She found that as a surprise, and working with the respective teams she discovered that people were avoiding taking responsibility because they were afraid of consequences.
Another major issue Jean has discovered during consulting was related to the difficulties encountered by the product owners. In an Agile environment, the product owner has to collaborate and negotiate effectively with the team, he has to appropriately prioritize the backlog tasks and make decisions he knows he will be accountable for.
Jean talks about RAPID management, a decision making process, which eases the burden of the product owner by being provided with reliable information and by sharing the responsibility with the team. RAPID stands for:
R - Recommender. One who recommends something to the decision maker.
A - Agreer. Someone who is not a decision maker, but who has a veto on specific topics.
P - Performer. The development team is made up of performers.
I - Input. Someone who brings in valuable information. The developers can play the R, P and I roles.
D - Decider. The product owner is the final decider, but he makes his decisions in the general context of the RAPID process, having more complete information and sharing responsibility with others.
Five Key Practices to Agile ALM
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
A Guide to Branching and Merging Patterns
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.
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