1. Detailing your features for your second client meeting What to put on your Google Group for them to review!

2. A. Verify the features you’ll do I’ll send a list of who signed up for what – by adding the names onto the non-duplicating features. Assume you got it right, in the meantime! For each of your team’s features: – Review at all the “duplicates” to be sure you captured all the meaning. – Be sure to include/determine urgency and criticality.

3. B. Add “surrounding” info to each feature In a sentence or two, write what the feature means to you. Paraphrase it! In a special comment, note what other features are closely related to this one. – Add to that note what other teams are working on those features! Add a comment about how the feature relates to the surrounding environment. Like, what does it accomplish, as part of a big picture.

4. C. Divide your features into smaller features This applies to the big ones, like, – “Student explores existing concepts and adds internship experiences.” Or, – “Student pre-registers for classes.” Try to identify components, as “sub-features.” – Could be pieces that add up to the whole thing. – Could be varying situations or alternatives.

5. E. Create a “user story” about each feature, or about the key part of it Do this for the main flow of the 5 most important features you are doing! Call this line of description “User story” to make it clear. Make it read like this: – "As a, I want so that “ – Like, “As a user closing the application, I want to be prompted to save if I have made any change in my data since the last save.” See website http://www.mountaingoatsoftware.com/topics/user- stories for additional information. http://www.mountaingoatsoftware.com/topics/user- stories

6. F. Do a storyboard and include it Pick the MOST important feature you are doing. Pick the MOST important flow that occurs in that feature. Draw pictures showing a sequence of events for that. Scan them in, if done by hand. Describe at least a sentence for each one. Be sure to identify where it fits in with your feature, like referring from the feature to this figure.

7. G. If possible, get your PM’s advice You’ll also be talking with them about HW 2, but Your Milestone 1 isn’t due to them till Friday. – It can be missing a few things, but it should be close enough that they can provide detailed advice.

8. H. Post features in your Google Group Make sure it’s a public document. Call it “Team Features.docx” (or some other file type your client could edit). Post there 24 hours ahead of your client meeting. I’ll notify your clients to go look on the Google Groups. Whew! That’s it. Note – this also can all become a part of your Milestone 1. The features are a good part of that.