website:
http://thebusinessanalystpodcast.blogspot.com/============================================================
Episode 004: Doug Goldberg Reveals Unit Testing, The Business Analyst Podcast
Uitgegeven: vrijdag 8 mei 2009 16:13
>> RSS Feed http://bapodcast.libsyn.com/rss<<
As you know this podcast series is geared towards an audience from for
beginners and experts. Both could learn new tricks from each other.
Before we continue a short message to the audience. During this BA podcast its my intention to discover all aspects of BA, as well as the fringes of BA. So not all episodes are 100% BA but, aligned to people or functions that interact with a BA.
If i am correct you have a technical background with Java, IBM Websphere. Was your transition into being a BA a choice or did it just happen..?
1. BA And testing. here in Holland they use a test method called TMap. What other methods are poplar, and whats a typical test procedure?
1.1 I'm curious to know your testing analyst experience. What does a test analyst do?
1.2 How is it related to BA?
1.3 Do they have interaction with each other?
1.4 When would a BA contact a Test Analyst?
1.5 What things would a BA and Test Analyst typically be speaking to each other about?
1.6 What are the most important things as far as Test Analyst is concerned?
-- towards BA,
-- and to its own team
1.7
I've done a few user Acceptance tests, where we put users in a room once
per week and they need to functionally test the apps. Thereafter I had
a user steering committee meeting where they reported their findings.
During this meeting i would also demonstrate new features to be tested,
and note their comments. Afterwards, take these comments to the
developers. Does anything of this procedure sound familiar to you in
the BA role? Or were you more involved this way as a test analyst? I'd
like your take on user acceptance testing.
2. test cases
2.1
Previously in my capacity as Information Analyst used Use Cases for
making test cases. For out American audience, here in Holland we have
Information- and BAs. The BA is more working for the sponsor, whereas
the Inf Analyst reports to the PM. In some instances a BA may be
leading a team of Information Analysts. Anyways, back to testing with
use cases.
2.2 Can you explain a bit about your experience as test
Analyst working with use cases. How would one construct a test case
from Use Cases?
2.3 What elements / "things" would you want to put
into a test case? Do u use test plans..? is it coordinated with PM, BA
or anyone else? How?
2.4 Assuming working on an Agile project with
RUP, in which stage would one be start to think about testing, and test
team, test cases..?
Duration: 25 minutes
Mediabestanden:
TheBAPodcast0004_Doug_Goldberg_reveals_unit_testing.mp3 (MPEG Layer 3 Audio File, 28.1 MB)
And how does this relate to Manager Tools?
Merasmus,
As you're a longtime member and have been active on the forums, you've some benefit of the doubt.
Were you new, this would be seen as unwanted spam.
Rather than cutting and pasting, you should relate what you're doing to the interests of Manager Tools members. Why would this be useful to us? How does it relate to the Manager Tools way of management.
You don't seem to have edited the content for us, nor to have provided us a reason to listen.
John Hack
Well I like it. About
Well I like it.
About time someone started giving out podcasted wisdom from the BA world.
Thanks!
(Okay, you could have edited the post to be more reader friendly)
Good and bad...
I like parts of what both John and Matt have said.
We're certainly opposed to these forums being used as advertising. Mike and I are here everyday, and we police things. That said, our community is wonderful, and is self-policed so well we rarely have to intervene. Rest assured, I have irritated many in the service of the community. A recent experience reminded me that power begets targeting software. I have been called names...funny, really.
And you'll notice we've not needed to have anything written down. Organic systems tend to be less amenable to such.
I like the idea that a long time member feels that there might be a benefit for other members in a new podcast (or other endeavor) and so posts on same.
In this case, though, it certainly could have been delivered more professionally, and with a sense of offering a benefit rather than what I can only describe (coming from Merasmus) as an inadvertent error in posting.
But we like our Dutch friends, and will take this opportunity to wish him well, and hope that some of our listeners tune in and benefit. (Not that we will always be amused, of course ;-) )