I think of specific systems expertise and general "possibilities of technology"-type knowledge as different rungs on the same ladder.

And I absolutely think it is incumbent on the BA to be able to break down the possibilities of technology in terms that business folk can digest. And to be able to do that, obviously, we have to have some of that knowledge ourselves.

Thanks for the comment, Alex.

Honestly, I am still fleshing out how "I" want to define the various "domains" of BA knowledge/skill - which may be non-standard anyway, so you're right I'm not sure that my usage of "domain expert" in this context is the best.

I think I'm pretty close to getting my stuff together, though, and if I can get some time this evening after the kids are down & before I crash, I'll try to post my thoughts.

Re: the differentiation "between between an analyst who focuses on a particular business domain as opposed to one can apply themselves to any domain" in career terms - I think that's part of where David wants to take the conversation. I'd certainly be interested in hearing everyone's thoughts on that as well.

Maybe a topic for a round of posts on our respective blogs?

I hear what you're saying on the domain shifts, David. I think there's a certain degree of technical know-how that you just pick up by working with systems in general over time, too. Regardless of the industry, you're well served by having a fundamental understanding of architecture, and the way systems work.

The analysis skills are the ones we can't do without, though.

I think that's a great suggestion for an upcoming topic, too. I think the vendor/software experience has a lot to do with multiple factors including - consultant vs. perm. BA for a company; consultant in a specific field or technology vs. general business analysis/project management consultancy, etc.

It is a conversation I think it'd be interesting to have. Just need to get my thoughts together on it, first.

You're most welcome. Thank YOU for providing all the great material. I love the wiki idea.

Funny! Yeah, the little ones love the youtube videos, too - chimpanzee riding on a segway.. Cat flushing the toilet, etc... What did we do without 'puters growing up, anyway?

Thanks for your comment, Suzanne. Thrilled to hear from you!

I'll gladly second the recommendation of Mastering the Requirements Process. It was one of the first books in my BA library and definitely provides some additional insight into requirement patterns.

I wasn't aware of the "Adrenaline Junkies & Template Zombies" one, though. I'll be sure to give it a look.

I don't think so, Craig. I tried telling her some user stories at bedtime once, and she just wasn't that into them.

Good stuff, Adam. Great idea on the initial article. It's been fun following the conversation here and over on your blog. I'll look forward to the new feature in Bright Green Projects!

Thanks for the comment, Ambika, and welcome to Practical Analyst. Agree that simple is good - as simple as possible, but no simpler!

Good deal! Glad to be of help!