Tools like Cucumber encourage driving new pieces of functionality through tests which cut through the entire app. As a consequence these Acceptance tests can be quite slow. This leaves us in a dichotomy, you want to keep adding new features to your product and you want to maintain rapid test feedback. Somethings got to give. Does Acceptance tests driven development scale?

What could “success indicators in the trenches” be, beside the different “agile maturity” measures? What are yours/ours best experienced indicators?

I propose you a build/ discovery process of what  success means for each of us on a everyday implementation of an Agile process.


–Arriving in London around 11:15 AM only —

Just in case anyone has Google Wave I’ve setup a quick wave for the event. If you don’t have a Google Wave account and would like an invite just reply with a comment and I’ll invite you.

On Google Wave search for: “Open Space London – Volcano Edition 2010” and it should show up.

Easier: Direct URL to the Wave

~ Cheers

Make your own changes

With the emergence of backlog-driven development techniques such as Scrum, Kanban and FlowChain comes the need to prioritise these backlogs for e.g. best ROI. Such prioritisation suggests a need for some quantification of both cost  (input) and value (output), and in particular, Business Value. Join this space to co-explore notions of value, both from rational (objective) and emotional (subjective) points of view.

Posted by: Bob Marshall (@FlowChainSensei)

We’d all love our users to have a good, even great, experience every time they use our software. Should we leave that to chance, or maybe to the intuition and innate skills of our UX folks? Or is there a more predictable, disciplined way to articulate the NATURE of the experience we want our software to evoke? And what about the other stakeholders in our development endeavours? What kinds of experience should we seek for these folks? And how to ensure that happens more often, too?

Posted by: Bob Marshall (@FlowChainSensei)

JonJagger How about if everyone going to #openvolcano10 networks with 5 who aren’t to think about how best to use the openspace (from me and Kevlin Henney)

flowchainsensei #OpenVolcano10 My topic suggestion 1: What is all this coding FOR, anyways?

flowchainsensei #OpenVolcano10 My topic suggestion 2: What makes for a highly-effective tech organisation?

@natpryce: I want #openvolcano10 to come up with a better name for monads

flowchainsensei #OpenVolcano10 My topic suggestion 3: Buyology, Emotioneering and the User Experience

flowchainsensei #OpenVolcano10 My topic suggestion 4: Notions of Value – can the rational and emotional co-exist?

stal_m @KevlinHenney what about documenting in agile contexts, agile architecture design, when to prefer functional prgr over OO #openvolcano10

JonJagger #openvolcano10 someone thinks of a world changing idea tonight, all attendees self-organize and build it tomorrow (I can wish for anything)

darrenhobbs #openvolcano10 I suggest ‘Humane software design’ . Why does software so rarely and so poorly reflect the way physical objects behave?

bernhardmerkle #openvolcano10: idea: what really motivates people (not only developers)…

bernhardmerkle #openvolcano10: idea: how to measure in agile teams (this is often not done IMO)

stal_m #openvolcano10: more about agility in large projects

A journey through the characteristics of development organisations at different stages of effectiveness.

Posted by: Bob Marshall (@FlowChainSensei)

A co- exploration of the purpose of software development, including a few radical ideas on the nature of a clean-sheet tech organisation (i.e. one not bound by prevailing conventions and ideas of management, etc.).

Posted by: Bob Marshall (@FlowChainSensei)

If I can wish for whatever I like I’ll have this:

How about if someone thinks of a world changing idea by tomorrow morning and all the attendees self-organize to actually build it in one day.