1. What do Goto and Cotler think are some important things to identify when assessing audience capabilities? Are there examples you would add given changes in the industry since the book was published in 2005?
In the book it is said that we have to know our audience and start determining their technical capabilities such as their screen resolution, latest realplayer plug in, what kind of browser, what bandwidth. They said that the goal is to identify target audience's technical capabilities. In doing so, we can set standards for the team to work within.
These standards must be in alignment with the expectations of the client. Keep in mind that your key client contact may not be the best person to answer these questions.
I feel that this book is a kind of old to this generation. But our grandmother might be able to still use an 800 x 600 screen. The book is a sort of not keeping up with today's trend, but I think it would be better to follow what the book said. we need to consider which plug in target audiences are using, what resolution their computer is applied to. When considering of today's trend, we can consider audience's internet speed, latest updated browser version.
2. What is scope creep?
Scope Creep is the slow, inevitable migration of a website redesign from a straightforward,
comprehensible project to an out-of-control nightmare. Seemingly insignificant modifications and
unplanned extra time spent handholding and baby sitting your client lead to budgetary increases and
time delays. Scope Creep is subtle; you seldom realize it is happening. At your kick-off meeting, define Scope Creep to both client and team and explain how the various schedules and delivery plans all work
together to keep the project on target.
3. What software application do the authors recommend using for project management? Why do they recommend using a different application to deliver project management information to a client?
Microsoft Project.
They say that Microsoft Project is an industry standard in terms of tracking multiple timelines and deliverables. The application's greatest strength is its ability to recalculate an entire schedule based upon a single change. If client feedback is two days late, the program will automatically construct a new schedule for all remaining tasks.
(I am not sure this is a correct answer cause this application is described other than pages 46-85)
4. There's a proofreading error in the sidebar titled "Project Management Applications"—what is it? (Google may help you here.)
It might represent that I forgot to do what I should have done before? or do I miss the appointment day with client? (honestly I don't know... OTL)
5. According to the authors, can usability testing be conducted using an online survey? Why or why not?
Book describes that there are many valid forms of feedback (focus groups, online surveys, etc.), but usability testing differs in that it shows what your audience actually does, not what they think they might do. If you're going to test, decide the scope of testing and get it in the schedule as soon as possible.
Online survey can make project team think their audience will behave,
but rather how an individual site visitor actually navigates, finds information, and
interacts with website.
However, usability testing is one-on-one test with actual site visitors, which is the best way to gather relevant data and real-world input. Conducting usability tests informally throughout a redesign and on
an ongoing basis ensures proper feedback and allows you to adjust accordingly for a
more successful user experience.
