Meeting Minutes



Date: |12/09/08 | |

|Location: |SE Project Lab and SE Team Rooms |

|Participants: |Professor Martinez, Bob J., Stuart Haas, Ryan Kao, Harmon Keener, Daniel Rabess, Michael Dack |

|Meeting Start Time: |4:00 PM (with Martinez) and 4:30 PM (with Bob J.) |

|Meeting End Time: |6:00 PM |

|Scribe: |Stuart Haas |

Meeting Agenda:

|Actual Time (minutes) |Estimated Time (minutes) |Activity |

|40 minutes |30 minutes |Kodak Kiosk Install / demo |

|5 minutes |10 minutes |Questions from demo |

|10 minutes |5 minutes |Team questions |

|10 minutes |15 minutes |Discuss development process |

|25 minutes |30 minutes |Project plan discussion |

|2 minutes |2 minutes |Closings |

Total time: 90 minutes

Meeting Discussion:

|Time Started |Discussion |Time Spent (minutes) |

|4:00 |Professor Martinez discussion of corrections to the way we document and pitfalls to watch out |15 minutes |

| |for. | |

| |Weekly status reports: | |

| |Ensure first and last name is on the time sheet | |

| |Ensure that the complete column is filled out | |

| |Ensure same notation for time period ex.: From 2008-12-1 through 2008-12-8 | |

| |Agenda: | |

| |Start time for each item | |

| |Mention of invitees of the meeting | |

| |Notes | |

| |Put notes into template 2 (this template) | |

| |Last weeks notes should be put in this template | |

| |MS-Project | |

| |If using this, use only for milestone view | |

| |Use of a spreadsheet may be easier to manage | |

| |Not ideal for granular tasks | |

| |Consider scraping this in favor of a new tool or method | |

| |Kodak | |

| |Kodak may have charts that they want, that we need to know about | |

| |Individual Presentations | |

| |Split up research work | |

| |Upon a week or so of research, each participant makes a power-point of what was learned and | |

| |the results | |

| |Suggested topics were: MS-Project vs something else, wpf vs silverlight, and expression blend| |

| |vs using only visual studio 2008 | |

| |Presentations may be useful for any learning that is accomplished | |

|4:15 |Discussion of each individual’s time spent. The following notes on the discussion were made: |4:30 |

| |Licensing issue of expression blend (if we use this, as it expression blend 2 only comes with | |

| |a 30 day trial for free) | |

| |Summarize any findings in ppts and post to the website | |

| |Check out photo-organizers old project which still exists on the se website | |

| |May opt to ditch use of MS Project in favor of a spreadsheet | |

| |Dan’s timesheet was lost: ensure that submissions are made and received | |

| |WPF’s API in Visual Studio 2008 was causing some confusion | |

| | may be useful for schedule’s | |

| |Use the same notation in documents | |

| |Specify items of activity, targets, and associations they may have | |

|4:30 |Demo of the Kiosk hardware, including the install. Notes: |40 minutes |

| |We have the G3 kiosk with a 2.3 ghz processor and 512 mb of ram, and uses Windows 200 | |

| |The G3 may be switched for a G4 or G4x later on that has P4 3.0 ghz processor and 1 gb of ram| |

| |running under Windows XP embedded | |

| |We have the latest 2.0 software sweet including support for the photo book, and greeting cards| |

| |No printing on the kiosk | |

| |Inputs: usb, sd cards, cd’s, floppys, and Bluetooth wireless | |

| |Literature on dry lab and wet lab differences was brought | |

| |Sample photo book was brought | |

| |Sample calendar was brought | |

| |Went through the 4x6 standard workflow | |

| |Went through the photo book workflow | |

| |Went through collage workflow | |

| |Configurable software: only some config options are exposed to kiosk owners, the other config | |

| |options are hidden from them but exist | |

|5:10 |Demo questions |5 |

| |Password creation for setup options and the OS are posted on the private google group | |

| |If we mess up the OS on the kiosk, a snapshot was taken that can restore the kiosk back to its| |

| |original state | |

| |Mention of checking out the target gestures ad for inspiration on UI 3d design ideas | |

|5:15 |Team Questions |10 |

| |Do the panes that pictures are split across always remain the same square shape? | |

| |No, they do not. However, the panes will always be rectangular but the shape of the | |

| |rectangles can change | |

|5:25 |Discuss development process |10 |

| |Schedule with milestones expected by Sunday Evening by Kodak | |

| |Sunday evenings are the due dates of any documents and artifacts that need to be reviewed by | |

| |Kodak | |

| |Holiday schedule: we will most likely need to choose research areas and prepare presentations| |

| |of lessons learned for return | |

| |Get code from previous project for use. Prof Martinez said he would get us the resource cd | |

| |from the last project | |

| |Expression blend 2: licensing issue that was mentioned earlier brought up again | |

| |Spiral Process chosen as plan for its dynamic iterations | |

| |We need to map the phases of spiral to our project | |

| |Prioritizing risks should be done soon | |

| |Complexity of tasks should be noted | |

| |Figure out what goes in what release, core and increments | |

| |May use a large iteration first followed by smaller releases | |

|5:35 |Discuss project plan |25 |

| |Charts that Kodak will need from us should be disclosed soon | |

| |Track tool should be investigated (mike said he would do this) | |

| |Story boards (wireframe, paper prototype, etc) are requested by Kodak by the end of Week 3 | |

| |(next week) | |

| |Website needs to be up this week | |

| |Logins for content on website was questioned by Bob. We will probably not need these. | |

| |Installer discussion through away the possibility of InstallShield because of costs and | |

| |licenscing and we will probably use Visual Studio’s method of packing the project into an | |

| |installer | |

| |Risk management doc should be drafted by next week | |

| |Priorities of release features is in the updated requirements list on the google group | |

| |Should nudging of images nudge the whole image or the individual splits? The whole image was| |

| |the answer. | |

| |The requirements list should have a column for complexity | |

| |Beta testing was mentioned and we may have to deliver a beta or alpha | |

| |Beware that not all nonfunctional reqs should be considered at R1 but may come into play as we| |

| |advance | |

| |The look and feel is up to us. Make this pretty and advanced as this project may be | |

| |inspiration for future kiosk UI designs. | |

| |“Communication goes a long way” --- Bob J. | |

|6:00 |Closings |2 |

| |Meeting with Kodak sponsors at Tuesday 12/16/2008 4:30 pm to 6 pm | |

Team Decisions:

|Decisions | |Date Added |

|Use the 2nd note template emailed to us by Prof Martinez | |12/09/2008 |

|Spiral Model chosen as the methodology | |12/09/2008 |

Action Items:

|Assigned To |Task |Date Added |Estimated Completion|Effort (Estimated) |

| | | |Date | |

|Stuart Haas |Ensure all documents affected by meeting are up to date. |

|10 |Follow up on previous action items. |

|15 |Split up research among team-members |

|45 |Discussion of task assignments and team assignments |

|30 |Any team work |

|10 |Discuss agenda for next meeting. |

Checklist for scribe:

• Tally the total time spent today

• Ensure header at the top is completed

• Check in this and all modified files!!

• Check in agenda.txt with new agenda

• Update documents that are affected by this meeting (i.e. Action Items, Decisions)

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download