CIS 466 Prototype 2

Set up meeting in CLA 4-27

Schedule and hold second Prototype session with your customer with Dr. Soe present, to present the secondl prototype based on your project design.

Prototype 2 is similar to Prototype 1,except:

• project now should have some functionality
• one result of meeting should be a list of final deliverables
  • after agreement at meeting, send list of deliverables to customer(s) and instructor.
  • final deliverables include:
    • project itself
    • documentation including final report
    • training of end users, which may include training materials, cheat sheet, on-line documentation
    • implementation of project, if appropriate
    • list of improvements, enhancements, or additions to project that were outside the scope of your project but which customer might want to make in the future.

When you schedule this meeting, offer the customer and Dr. Soe several possible meeting times

• Monday & Wednesday: 1 - 4 PM; other times by arrangement
• Friday: 1-2 PM; other times by arrangment

Preparation for Prototype 2

Goals for Prototype 2

• Present the current requirements, analysis and design of project deliverables that your team has prepared for customer and instructor review
• Receive feedback, uncover further requirements, modify list of deliverables, modify project scope.
• Elicit decisions from customer
• Define open issues, and responsibility for their resolution, and dates by which open issues must be resolved
• Define final set of deliverables for project by end of this meeting
  • team will have a clear understanding of what they will deliver by end of quarter
  • send a copy to the customer so customer knows what will be delivered
  • send a copy to instructor
  • include the list of final deliverables in report 3

Presentation Norms:

• Be sure to have a printed agenda for your meeting with each team member's name listed next to category of questions or role team member plays during meeting
  give a copy of agenda to instructor - used for notes for grading purposes.
• Dress code: Business dress - business casual ok (no sneakers, tee-shirts, shorts)
• Everyone plays a role
• EVERYONE TALKS!
• Project manager presents short recap of project planning and actuals
  • High level report chart showing hours/costs per week or by project phase
• Other team members present parts of prototype -- put into agenda with team members' names and approximate times
  • Be sure person presenting prototype section can answer questions about it.
• Students who are shy about speaking should practice beforehand
  • write out an outline of what you will say
  • write out the first paragraph -- memorize it to get over initial shyness
  • Practice in front of a mirror - time how long it takes
  • Speak loud and clear -- and not too fast
  • Remember:  The more you speak in front of people, the easier it gets!

Your team responsibility is to conduct the meeting.

• Demonstrate the prototype of your plan for your customer.
• Include appropriate material, which will vary based on project requirements:
  • GUI interface design
  • Report design
  • Network diagram
  • Report on research on technology solutions for customer needs
  • Present appropriate diagrams and project requirements
    • UML
    • Business rules
    • Data dictionaries
    • ERDS
    • form designs
    • test design
• Get customer feedback - leave time for the customers to respond
• Revise project requirements and design to accommodate customer
  • Be accomodating, but manage requirements so that project does not grow too large
  • help customer to prioritize requirements as new ones emerge --
    • some requirements are essential to project's success
    • others are nice to have but not essential.
    • indicate that after this meeting you must "freeze" requirements, so customer needs to really think about what they need.
    • When customer wants to add significant new requirements, indicate that you must figure out holw long the work will take
    • If work takes too much time, customer may have to drop some other requirement

Have all members participate in the meeting --put them on the agenda.

Have one of your team members, who has good communication skills, take notes during the meeting.

• Use a laptop for notetaking -- then the notetaker can group decisions about similar parts of the project together.
• At the end of the meeting the notetaker can list the decisions and open issues from the meeting.
• Organize the notes still more and send them via email to customer and to Dr. Soe -- this really impresses customers and also reminds them of any open issues to which they need to respond.
• Send list of final deliverables to customer & instructor after meeting
• That will clarify for your team, your customer, and your instructor what to expect at end of quarter.