Okay, so let's wrap up this UX analysis and planning module with a review of some of the key points from the lectures that we just went through. We talked about an introduction to this phase, why we do this analysis and planning. It's primarily around making sure that we have the right scope and objectives for our project, and that were aligned with the people that we're delivering the project to. We talked about the difference between waterfall and agile projects. Different rhythms really to how the projects are delivered. Most importantly, you need to understand what successes are for given project, and you need to understand the organization, and the team that you'll be working with, as well as any constraints around the product and the brand for that product, as you start to pull your design together. We also talked a little bit about the importance of multidisciplinary teams, having different people that would contribute different parts to the project, and that all important contribution from our users or use of surrogates. Then we went into the methods for this phase. The methods are pretty basic, project plan, overview, and brief. These are just ways to make sure that the definition for the project is shared by everybody that has to work on it. Probably more important is the stakeholder interviews where you're actually talking to people about what their expectations and needs are. Then there's some methods for getting your view of the project across; elevator pitches, the artifacts from the future, the Pecha Kucha presentation. The Kano model lets you narrow in on some of the key elements to the project, and then the kick-off meeting really sets the stage for getting the project going. The most important method probably though is the work breakdown structure, which we talked about them in a separate lecture. The reason that that's so important is that it really frames the scope for what it is that you're going to deliver. We talked about how and when to use it. We went through the difference between the graphical style on the text style of WBSs. We talked about the fact that you could use it for team-building, to get buy-in for the project, to control scope creep. There's also some rules of thumb around WBSs that should represent a 100 percent of the work. The tasks should be limited to 80 hours or less, two-week tasks. We talk about the different possible levels for WBS, breaking them in new activities, tasks, and sub-tasks. Some of the tools you might use, and this method called T-shirt sizing, where you're estimating how big an effort, or the cost for an element in the WBS might be. You'll see that one again when we get into the project for this module. We snuck in embedded interface components. It's not really a planning thing, it's more of a toolkit that you'll have the building blocks for putting together systems that you design. We talked a little bit in here about how computers and devices see people and how we see them, inputs and outputs. Some of those specific elements that you might choose from physical controls, screens, audio output, voice user interfaces. Some of the more esoteric choices like gestures, tactile output, using vision as part of the system. Hopefully, after you've reviewed this lecture, you'll be able to think about the strengths and weaknesses of the different components, how they might impact users, what limitations they might have for certain users, and then some of the criteria that you can use when you're trying to include these components in a design. The project for this module, again, is focusing on some of the more common elements that come up during this part. First, is your choice of either a project brief or a project overview. Which is really just a way to lay out some of the most key elements of the project for people to review, and make sure everyone's on the same page. You can pick which one you want to do. The brief is more of a poster type presentation, the overview is more of a textual report. Whichever one you pick, you're going to use our fictional automated pill dispensary as your topic. Then you're also going to do a WBS for that project using the UX phases that we outline as common to these type of device projects. You'll pick the methods that you want to include in the WBS. Then you'll also do sort fictional estimate of the effort in order to try out the t-shirt sizing. So you've got a quiz to do, you've got a project to do. Our next module is going to go over UX research. This is really understanding our users. Please remember if you need help, don't hesitate to ask. Thanks you so much.
