Discussion of your planned project

• What is the big aim - your overall philosophic goal.
• Title
• Pitch
• Longer description (can include wireframes and userflows if necessary)
• Deliverable
• Constraints (limitations) - and how you'll solve them
• What knowledge expertise, capacity, do you need to complete the project that you either have or know how to get.
• What knowledge aren't you sure how to get, possible issues you might run into timetable
• Timeline
  

Planning

• Elevator pitch
• Identify your constraints
• Time
• Resources

Technology and people

• Any budgetary requirements
• Scope

What exactly will your final deliverables be, to guard against feature creep?

• Project WBS:  Your work breakout structure. 
• Your schedule on what each step will be, what are the deliverable from that step, and how long will each step take.
  

Requirements

• Identify a sample of who your users will be. 
• Who will be your testing group, either internal or external, who will help keep your project grounded in reality
• Use either qualitative or quantitative methods to find out from them what are the qualities that your project will need to be a success. 
• Identify any unusual system requirements, resources, or skills you will need to procure or get access to

Early stage Analysis and design

• Create at least one user scenario based on your vision of how people will use your project
• Create a basic userflow diagram for your system
• Wireframe the important states of your system, be they screens, interactions, or physical configurations

Completing the Agile circle:

• Return to your User Requirements testers and walk them through your userflows and wireframes.  Prepare to incorporate their feedback into the next round of design.

Presentation 2 (45 minutes)

The middle. Update us on your progress, problems, revisions, and problem solving status.

• Overall philosophy and elevator pitch
• What are you planning to show
• Updates and changes
• Progress: where you're at now/Current issues
• Update of schedule
• Conclusion

Completing the Agile Circle

• Update your plan, analysis and design based on the tester feedback, and incorporate the class feedback from the last presentation.

First round Implementation

• Create a rough implementation of your project, a first draft.  It does not have to be perfect or complete, but it does have to reflect the final form the project will take.

First round testing and evaluation

• Seek user feedback on your design.
• Tell us what you’ll fix for the final version of the project, and make any updates to the project Plan and Design required

Presentation outline:

• Title
  
  
• Elevator pitch
  
  
• Demo or thorough walkthrough of your project. 
  
  
• Philosophic background - Why is this project important, and why is it important NOW
  
  
• Original Hypothesis and eventual findings What were your assumptions going in to this project
  
  
• Experimental process What did you do to get here. What were your biggest challenges?
  
  
• Evaluate your successes and failures Remember, by failures we mean your findings. Places where your hypothesis was proven wrong due to experimental failure. Remember, it's not a failure, it's a finding.
  
  
• Conclusion
  
  
  • Call to Action What are the future implications. What are your next steps - if someone was to continue the work you've started, who should they be and how should they do it.
    
    
  • Give credit where credit is due