Project Outline City of Mountain View – need image !

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 1 Contents  Overview of Project  Introduction to City and Key Sponsors  Project Teams  Project Deliverable and Activities  Project Resources

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 2 Course Project Outline In this course, students will design and prototype a proof of concept for an innovative use of information-technology to meet a need for citizens of Palo Alto or Mountain View. They will work with people in the governments of those cities as well as with people who will use the services. The goal of the project is to explore ways in which new interfaces and architectures for interactions with multiple services can provide integrated support for activities that matter to the citizens. The class will be divided into two teams, each working with one of the two participating cities. Within each team, sub-groups will be assigned to: designing the solution from the user’s perspective; implementing the technical aspects of the system; and addressing the real-world economic and implementation problems in the larger context of organizations and information systems. Membership in these subteams will be determined by students’ relevant background and skills, and each subteam will also have opportunities to learn about the other dimensions. Representatives from both cities will be involved throughout the course, and will be available for feedback and interaction with the project teams. We will also have additional technical support for interfacing with existing enterprise systems, and teams will be provided with coaches, whose experience in design and software engineering can be a resource for learning. The project activity will be organized around a series of scheduled milestones for a sequence of design phases, at which teams will describe their progress and get feedback both from staff and other students. At the end of the course, we will invite other faculty, representatives from the cities, and people from the software industry for a formal presentation of the solutions.

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 3 City of Palo Alto Project Contacts at City of Palo Alto Carl Yeats (Director of Administrative Services) Frank Benest (City Manager) Additional relevant city information

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 4 City of Mountain View Project Contacts at City of Mountain View Nadine Levin (Assistant City Manager) Tom Forstreuter (IT Manager) Patty Kong (Assistant Director) Additional relevant city information

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 5 City Project Team Need Finding Sub Team: A critical element of any software development effort is to gain a deep perspective into the needs of end users. Often this step is shortchanged resulting in software that may be at best difficult to use, or at worst not meeting the core requirements of the intended audience. This sub team will lead the effort to understand the needs of end users– the citizens– as they pertain to the selected business and engagement scenarios. Prototype Design Sub Team: After gaining a basis understanding of the needs and requirements of end users, the Prototype Design sub team will lead the effort to design the optimum solution. The design process will go through various levels of prototypes and iterations including discussions with the City sponsors, end users and other various stakeholders. Real World Sub Team: To often focused need finding leads to elegant design which may end up in a solution that cannot be implemented. This could be because of technology fit, lack of planning on resources required to deliver, or other “real world” considerations will take a holistic look at the project and determine what needs to be in place for the city to realistically deliver on the proposed solution design. City Project Team: A team of students each will be assigned to each of the City projects. City Project Team (CPT) will be divided into 3 sub teams to ensure proper focus to critical aspects of the software development lifecycle. All teams and team members will work on all the tasks though each of the 3 key aspects will be led by the core sub team. (eg. For need finding, the “Need Finding Sub Team” will be in the lead while members of the other 2 teams will provide support.) Each sub team will be required to nominate a “Sub Team Lead”. Together, the 3 nominated “Sub Team Leads” form the leadership of the City Project Team and are responsible for guiding and coordinating the activities for successful achievement of the project.

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 6 Project Teams (sub team lead underlined) City of Palo AltoCity of Mountain ViewRoles  Students 1-4  Students 5-8  Students 9-12 Terry Winnograd Zia Yusuf  Students 5-8  Students 9-12 Hasso Plattner Sam Yen Need Finding Prototype Design Real World Course Sponsors

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 7 Project Work and Activities by Course Date DateCourse SessionProject Session Wed. April 4 th Introduction  Introduction to high level description to project  Meet with sponsors from City as brief introduction  Provide Project Overview Document Sat. April 7 th Design Exercise  CPT project work Mon. April 9 th Business Process  Project Time in Class: 30 min  Disclose project teams  Communicate expectations of “Scope Finding Phase”  Define deliverable for Wed. April 18 th Meeting with City  Students to begin “Scope Finding Phase” with citizen interviews  Team leads need to set up initial 1 hour con call with City Sponsors prior to Monday April 16 th. Wed. April 11 th Good and Bad of Software Systems  No formal project discussion. Outside class coaching sessions Mon. April 16 th Need Finding  Project Time in Class: 90 min  Teams present initial findings of “Scope Findings phase”.  Discuss strategy for individual city meetings on Wed April 18th Wed. April 18 th Civic Information  Meetings held at City offices with full teams and City Sponsors. 3 hour meeting where scope of project, key deliverables, mutual expectations etc. are set.  Possible Agenda: 1 Hour students present “scope finding results”- 1 hour Cities present needs from their perspective- 1 hour discussion to agree on focus areas and scope of project Mon.-Tue. April th Sapphire Visit  CPT team use Sapphire as a place to supplement their project knowledge—meeting with other city govt. officials, meeting partners that may have relevant solutions etc.

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 8 DateCourse SessionProject Session Wed. April 25 th Design Ideation  Project Time in Class: 60 min  CPT teams report back on results of Civic Information workshop and deliver project proposal and plan. (30 min each) and written document on plan Mon. April 30 th Building Software Solutions  No formal project discussion. Outside class coaching sessions Wed. May 2 nd Prototyping  Project Time in Class: 60 min  Present and discuss results of “Need Finding” on the agreed upon Use Case Mon. May 7 th Scenarios, Testing and Validation  No formal project discussion. Outside class coaching sessions Wed. May 9 th Developing Real Systems  Project Time in Class: 90 min  Invite City Reps  Students present early “Solution Prototype” Mon. May 14thSoftware Economics  No formal project discussion. Outside class coaching sessions Wed May 16 th The Future of Software  No formal project discussion. Outside class coaching sessions Mon. May 21 st Project Work Time  CPT meetings with City Sponsors at D School  Students work with their city sponsors on all aspects of the project Wed. May 23 rd Project Report  CPT dry run presentations (30 min each)  Class discussions

SAP CONFIDENTIAL © SAP AG 2007, 2006 Ecosystem in Review / 9 DateCourse SessionProject Session Mon. May 28 th Memorial Day  Memorial Day Wed. May 30 th Storytelling  No formal project discussion. Outside class coaching sessions Mon. Jun 4 th Final Presentations  CPT final presentations  City Sponsors present Wed. Jun 6thSummary and Reflections