By coincidence, I just read the first 4 chapters of the book today in preparation for an interview (prod. manager role). I see it being straightforward for enhancements. However, for sites being built from the ground up, it could get pretty tricky no? In my experience, it is the Information Architects that put the site together as far as flows, wireframes, user experience, front-end.. that kind of stuff. The first 4 chapters didn't mention any of this, only the upfront IA activities of defining user roles and user personas. Maybe I'm missing something (I saw that the later chapters delved into the development aspects of Agile), but this I think is a big part of tying the entire site together. How would customers be properly informed of coming up with user-stories and prioritizing them w/o those IA steps I mentioned? I've never practiced Agile, so am very curious how IA roles tie in here because alot of times, Product Managers also play the IA part on projects (depending on their exp.). Anyways, I think the book is good, but I feel it simplifies the usually very important steps prior to the coming up with the user stories. If I can be convinced of this, then I can see how Agile can be implemented in organizations where the IA role is considered important.