Boardmad

Here’s the eternal question…how do you get technologists to intimately comprehend the business process and function in order that their finely-honed code can help do things quicker, cheaper and more accurately ?
This is largely the role of the Business Analyst. I’m getting heavily involved with my employer’s BA cadre grinding out a Best Practice bible in order to share experience.

I’m part of a larger group, looking at the nature of ‘Requirements’. In the broadest sense possible this covers everything from what is one, how do you define a good one, how do you get them, how do you test what you’ve got and what do you do with them once you got them, validated and tested them…so it’s all building into something a little more complex than one might think !

However this is where I tend to start sticking my oar in and muddying the waters a little. All this conjecture and academic analysis is useful and vital from the stated aim of the group - to share ‘Best Practice’…however my proximity to Business users, while staying intimately involved with the technology and infrastructure we reside upon makes me take a more measured and pragmatic view.

It’s going to be interesting to see how pragmatism and MoSCoW principles will sit alongside these plans, requirements-gathering methodologies, ellicitation tools etc !