InfoQ

News

Interview: Jean Tabaka About Team Collaboration and RAPID Management

Posted by Abel Avram on Aug 01, 2008 04:10 AM

Community
Agile
Topics
Collaboration ,
Adopting Agile ,
Teamwork ,
Agile Techniques
Tags
RAPID

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.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Watch Thread Reply

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.