[Sigia-l] IAs vs BAs

[Matthew Hodgson]

What about Jesse James Garrett's job descriptions for IAs - http://www.jjg.net/ia/files/iadoes0700.pdf?

Maria Horrigan also talks about BA stuff here: http://gettingsystemsright.wordpress.com/. She notes that for many BAs the process stops after they've delivered the requirements document.

M

________________________________________
From: sigia-l-bounces at asis.org [sigia-l-bounces at asis.org] On Behalf Of Juan Ruiz [juan.ruiz at ceo.syd.catholic.edu.au]
Sent: Tuesday, 19 June 2007 4:02 PM
To: sigia-l at asis.org
Subject: Re: [Sigia-l] IAs vs BAs

Mathew, your blog regarding IAs and BAs is good. It does clarify some of
the differences between IAs and BAs, especially when you say that BAs
concentrate on business needs, and IAs concentrate on information needs.


The concept though, bottoms down to what the organization is expecting
from the employee (either BA or IA). An organization would like to have
a BA that can do IA. I assume they will have more preference for a BA
role because this role has existed longer than the IAs, more
documentation exists on their deliverables, and their business knowledge
helps them to be closer to PM methodologies. I see a lot of job postings
for WEB BAs or BAs who have experience with Wireframes and UCD. Isn't
that what the IA should do?

As Andrew said, as an IA we have to wear many hats (perform different
duties such as IA/BA/PM/UCD...), but is there a way that I can
differentiate my documentation from a Web BA?

I found that in order to get the 'buy-in' from my stakeholders, I have
to convert my IA research and documents into BA document types, which
they are familiar with.

Thanks for your responses, I feel like soon I should be able to defend
my case between IAs and BAs.


-----Original Message-----
From: Andrew Boyd [mailto:facibus at gmail.com]
Sent: Tuesday, 19 June 2007 3:44 PM
To: Juan Ruiz
Cc: sigia-l at asis.org
Subject: Re: [Sigia-l] IAs vs BAs

On 6/19/07, Juan Ruiz <juan.ruiz at ceo.syd.catholic.edu.au> wrote:
> Where do we draw the line? I find that because BAs look more into the
> business side of things and their work is more aligned to Project
> Management methodologies, their opinions weight more than from an IA.

Juan,

the other threads on this topic (and similar) usually ended, after
much bloodshed, with the following conclusions:
1. It all depends - there is no one set of rules for what constitutes
IA/BA/PM/CM/Designer/designer/UCD/UXD.
2. The labels are arbitrary: I have myself performed what others might
term IA tasks today, as well as BA/PM/BPM/BPI/UXD/Big D Designer ones
- happy to discuss specific instances. And it's not even 4PM here yet
:)

Cheers, Andrew
---
Andrew Boyd
http://facibusreviews.com


____________________________________________________________________________
This e-mail is intended for the use of the addressed recipient(s) only and may contain confidential and privileged information. If you have received this message in error, please delete the message and any attachments and copies immediately; and notify the sender by return e-mail.

Any views expressed in this message or any attachments are those of the individual sender and do not necessarily represent the corporate opinion of the Catholic Education Office (CEO), Sydney.

The CEO Privacy Policy is located at http://www.ceo.syd.catholic.edu.au
____________________________________________________________________________

------------
IA Summit 2008: "Experiencing Information"
April 10-14, 2008, Miami, Florida

-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. The recipient should check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. Thank you for your cooperation.