The application I am currently working on is going through dramatic changes, which reflect the change in the organisation as a whole. Nothing new about that of course. It is interesting, and a credit to the people that built the application originally, that much of the change required can be achieved through configuration and modification to reference data. Quite alot can even be done by the business users themselves. That’s not to say it has been easy to define what we need to do though, as it absolutely hasn’t been.

But my question quite simply is this: Should one attempt to employ BDD in this sort of situation? I have attempted to, but quite frankly, it is hard and unwieldy. I am not convinced it is even assisting us. What is required is some means of describing what is currently there and explaining simply and easily what changes we need to make.

This could be done as a simple check-list – which perhaps is all that is needed?

I am not an SAP person, but to widen the question, can you use BDD successfully on a SAP system, given that SAP is probably the archetypal case of achieving changes through configuration rather than development as such (I suppose a more dramatic example of my situation). The paradigm with SAP tends to be about the organisation adapting to the software, rather than forward-engineering “features” which is what BDD it seems to me, is geared towards. So should one attempt BDD here? I suppose I ought to just go downstairs and just ask the SAP team.

« »