I wrote a short article about the relationship between the IA and the sitemap, where I compare it to the Genotype-Phenotype relationship.

I argue the concepts should NOT be used interchangeably, even though many do.

Hope you enjoy it:
http://aaronrikower.com/blog/2011/06/ia-and-site-maps/

However, to be fair, it should be understood that the examples provided fall well short of what
is expected of a professional usability / information architecture resource.

I know for sure that my IA delivery packs are extremely comprehensive.

IA does also need to follow a formal approach and not enough is said about this. The standard
business analyst approach fairs well with the following deliverables: As-Is (snapshot of what we
have to day, heuristic evaluation), To-Be (what we are looking to do), Gap Analysis (the difference between As-Is and
To-Be), Business Requirements (what does the business functionally want and what are the priorities), Non-functional requirements (what other requirements are there e.g. training, business process change), Design documentation (User Design Documentation) etc …