A Formal Performance Tuning Methodology: Wait-Based Tuning
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Aug 01, 2008 04:10 AM
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.
The Future of Software Delivery According to visionaries Grady Booch & Erich Gamma
Lean Software Development Governance, a whitepaper by Per Kroll and Scott Ambler
Offshore software development: Making it a success with Agile Practices
Rational Team Concert v1.0 Standard Edition trial
Webcast: Achieving True Agility -- How process can change the behavior of your tools
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.
In this article, Jim Webber, Savas Parastatidis and Ian Robinson show how to drive an application's flow through the use of hypermedia in a RESTful application.
Eccentric artist turned overnight anti-celebrity, Giles Bowkett captures the heart and soul of RubyFringe as he demonstrates his revolutionary Archaeopteryx MIDI drum pattern generator.
InfoQ Chief Architect Alexandru Popescu discusses the InfoQ architecture, WebWork and DWR, Hibernate and JCR, Hibernate scalability, the new InfoQ video streaming system, and future plans for InfoQ.
The Worldwide Large Hadron Collider (LHC) Computing Grid provides data storage and analysis for the entire high energy physics community that will use the LHC.
Scott talks about software craftsmanship represented by people responsible for their work, continuously learning, taking pride in their work, sharing knowledge and respecting professional standards.
Eric Nelson explores Windows as a web platform using IIS 7.0 providing an architecture deep dive and striving to reduce the lines of code in web applications.
No comments
Reply