collaboration Archives - Page 2 of 2 - EBG Consulting

Being Agile when Designing and Playing Agile Games

In my Stickyminds.com column “Playing at Work: Agile Games Deliver Value” I share game ideas and experiences – the benefits games can provide, selecting an appropriate game, facilitating a game, and designing a winning game.

Designing and Facilitating Agile Games

When writing the column I got to thinking how agile principles could provide a basis for good game design and facilitation. I reflected on a recent experience I had at Deep Agile 2010: Empowering Teams with Agile Games. Working in a small group we created a new game, tested it, and retrospected both the game and our design process in less than half a day. We consciously (and some times unconsciously!) were being agile! (To see and learn more about our game, read Michael Sahota’s summary at The Backlog Is in the Eye of the Beholder.)

Games and The Agile Manifesto

To clearly communicate the agile-ness of our work and what we learned I did a quick mapping to the Manifesto for Agile Software Development.

The 4L’s: A Retrospective Technique

by Mary Gorman and Ellen Gottesdiener We liked it when a good thing took on a life of its own. We learned that it really resonated with many folks. We lacked sharing the full understanding of the technique. We longed for more sharing. Liked — Learned — Lacked — Longed For At the recent Deep…

Agile Requirements: Not an Oxymoron

Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons—self-contradictory phrases, often with an ironic meaning.

Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?

Once More into the Breach

Traditionally, defining requirements involves careful analysis and documentation and checking and rechecking for understanding. It’s a disciplined approach backed by documentation, including models and specifications. For many organizations, this means weeks or months of analysis, minimal cross-team collaboration, and reams of documentation.

In contrast, agile practices—leanLean, Sscrum, XP, FDD, crystalCrystal, and so on—involve understanding small slices of requirements and developing them with an eye toward using tests as truth. You confirm customers’ needs by showing them delivered snippets of software.

Lessons on Collaboration: Retrospective on Delivering the IIBA BABOK, Part 1

What are good practices for delivering a complex product for a broad global customer with a group of volunteers scattered all over the world?

This is a real-world question for me right now: I’ve volunteered to participate on the Agile-BABOK® (Business Analysis Body of Knowledge) addendum effort. Like the BABOK itself, this addendum can impact the practices of a broad worldwide community of professionals.

Learn From Those Who Have Been There Before

Two groups have tackled the problem of using volunteers to deliver an industry standard, so I figured we should “learn before we burn”. One group is the PMI Agile Community of Practice group, and the other is the BABOK Body of Knowledge Committee.

Ideally, learning what worked for these groups, along with their suggestions for what they would do differently were they to do this again, could help the Agile-BABOK addendum effort to start smart: leverage what they’ve found works, avoid or mitigate what didn’t work, and adjust their practices based on their experience.

Posts tagged collaboration

Being Agile when Designing and Playing Agile Games

Designing and Facilitating Agile Games

Games and The Agile Manifesto

The 4L’s: A Retrospective Technique

Agile Requirements: Not an Oxymoron

Once More into the Breach

Lessons on Collaboration: Retrospective on Delivering the IIBA BABOK, Part 1

Learn From Those Who Have Been There Before

Form Heading

Lists*

EBG Product Agility Newsletter

Get tips, stories and news on product discovery & delivery