InfoQ Homepage Collaboration Content on InfoQ
-
Unconsciously Agile? (Rhythms of Agile Development)
Damon Poole wrote recently that many of us maybe practicing Agile development without even realizing it. It turns out that many of us maybe showing signs of the Agile disease without knowing it.
-
Agile Beyond the Workplace
Many of us in this field have had our work habits affect our family life - many times for the better. Some of us use index cards in their daily life for scheduling, prioritizing, and discussing daily tasks with their families. Peter Abilla blogged about how he uses a Job Chart (a type of information radiator) to teach his children.
-
Successful Collaboration Doesn't Happen by Accident
Partnership Coach Michael Spayd tells us that both contractors and permanent employees can find themselves playing a "consultant" role, and should consider using consulting contracts or "designed partnerships" with their clients - not regarding the exchange of money, but to create a climate for stellar results for the client, while also communicating their own values and preferences.
-
I'm Not Sure What You Heard is What I Thought I Said
Are family celebrations a challenge? You get together to catch up and swap stories, and invariably something gets "taken the wrong way." It's not restricted to families is it? So it's not surprising that the Satir Communication Model jumped the fence from family therapy to team building! J.B. Rainsberger uses an amusing Christmas-at-Walmart anecdote to illustrate its use.
-
Can architecture create a gap between developers and software they build?
Many software project management and architecture approaches tend to parcel out work on a project in a way to create hierarchical layers. This helps simplify both developers’ work and management. However, the underlying information shielding among layers can potentially create a gap between developers and the software they are building, if their tasks are totally taken out of functional context.
-
InfoQ Presentation: Jean Tabaka on Surviving Meeting Burnout
Teams moving to an Agile approach may feel irritated as they move from command-and-control to a collaborative culture - which can start to look like non-stop meetings, starting first thing every Monday morning. In this InfoQ exclusive presentation, recorded at Agile2007, Agile coach Jean Tabaka shared her experiences working with teams, offering guidance on how to alleviate meeting burnout.
-
Holding a Program in Your Head
Your code: is it that stuff you store in version control or, as Paul Graham argues, "... your understanding of the problem you're exploring"? Graham has written an essay offering eight suggestions for developers trying to understand the code on which they're working - some of which seem to contradict the advice of the agilists.
-
InfoQ Book Review: The Responsibility Virus
Agile teams can use a regular learning cycle to shift gradually and organically into a more collaborative mode. But the rest of the business may not be equally well equipped. Deborah Hartmann proposes that the Responsibility Virus is an important book for the change agent's library, suggesting that it may provide a tool to help other parts of the organization also grow into greater collaboration.
-
Coding Dojos to Master the Art of Development
Coding Dojos are meeting places where developers can go to practice coding together and improve their development skills in a relaxed and enjoyable setting. Emily Bache and others have started to document dojos on a wiki where the public can go to get started.
-
InfoQ Article: Lean Kanban Boards for Agile Tracking
"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.
-
InfoQ Interview: Experiences with Planning Poker
In this fourteen-minute interview, Nils Haugen described "Planning Poker," a simple mechanism for arriving at estimates collaboratively, which has additional team building benefits and improves team estimates over time. Haugen shared his views on why this technique is an important tool for Agile teams in this InfoQ interview.
-
InfoQ Article: Creating a Collaborative Workspace
We may imagine an extremely Agile team as working in a minimalist teamroom, surrounded by whiteboards. But that isn't enough - some of the comforts left behind in our traditional spaces were there for good reasons. In this InfoQ article several experienced coaches offer advice from experience, on creating collaborative team spaces that work.
-
Working with Mingle
InfoQ had some time with Mingle project engineer Jay Wallace, to use ThoughtWorks' much anticipated Mingle software and demonstrate to us how it differentiates itself from other products by being a truly agile project management tool.
-
XWiki 1.0: Extensible Java-based wiki/application platform
XWiki is an open source wiki and an application platform written in Java and released under LGPL license. Its development platform features allow creating collaborative web applications and also provide packaged applications built on top of the platform (second generation wiki). XWiki 1.0 launched last month, but there have been almost 10,000 deployments to date.
-
Can Virtual Teams Ever Work?
Co-location is one of the cornerstones of Scrum, so the increasing trend toward non-co-located teams raises questions on how Agile can work in such an environment. David Churchville has blogged some common distributed team scenarios, and offered solutions to common pitfalls of delivering Agile projects using different types of distributed teams.