By Tom HolubAcademic units generally lack the capacity to develop complex applications to support their work. With limited funds and few local technical resources, they solve business problems through a patchwork mix of Google Docs, Facebook pages and Eventbrite sites. These ad-hoc systems are labor-intensive, idiosyncratic, and often frustrating to both the department and the target audience. Occasionally during my time at Berkeley, a department chair would ask if we could get Engineering students to build an application for them. Berkeley does have many brilliant engineering students who will go on to have distinguished careers in software development; why not tap their expertise while they are here? The idea is appealing, but it is usually difficult to find a fit that works for both the department and the student developers. Engineering programs require student projects to be creative and challenging; they are not structured to provide production-quality productivity applications. As Dan Greenstein put it, “If it works, it’s not research.” This year, I had the opportunity to support a group of students from Berkeley MEng program who made their research work. The Fung Institute’s one-year Masters of Engineering program is structured around a team-based capstone project. In 2017–18, the program matched 90+ sponsors with three to six person student teams, who developed their skills over the course of the year as they took their projects from loose conception, through design and development, and all the way to implementation. The team I worked with was matched with a project sponsored by the Berkeley Arts+Design (A+D) Initiative. A+D is charged with increasing arts engagement among Berkeley students, and viewed the Fung capstone program as an opportunity to explore the possibilities of an arts engagement platform without a huge financial investment. As a process consultant helping guide the team, I got to watch the process unfold, and saw the enthusiasm the students brought to the challenges facing them. The experience gave me a better understanding of how this kind of student capstone project could successfully contribute to a program at Berkeley, despite substantial constraints. The three major constraint areas I observed are:
1. ScopeThe Fung program confers a Masters of Engineering degree, which means that the project must be of sufficient technical creativity to win the Institute’s approval as a capstone, but small enough to be plausibly completed by the student team. Many departmental projects have significant organizational complexity, but not enough technical complexity to qualify.
2. Limited timelineCampus projects tend to have sliding timelines, but degree programs have firm end dates. Over the course of the year, the project deliverables must be able to shrink to accommodate the student team’s ability to deliver them.
3. Student capacityEach team has a different composition, but most students enter the program with little experience of developing professional-level applications. Learning through the course of the year is, of course, the very purpose of the capstone project. There are likely to be stops and starts as the team gains a better understanding of the task they are charged with. The capstone is also a minority of the students’ total work in the program, so they are constantly juggling other assignments, readings and exams while making progress on the capstone. Given these constraints, the A+D team did a great job building an application which successfully went live to the public (and looked amazing!), on time and on budget. Beyond their individual dedication and talents, I’d attribute their success to:
1. Creative thinkingPartly because the students came from varied backgrounds, they approached the project expansively, conceiving of numerous possibilities for the scope and the solution, and helped the sponsors flesh out their own ideas.
2. Student experienceThe strategic goal of the project was to increase arts engagement among students. Because they were part of the target audience, the team could act as a built-in focus group, thinking about what they and their friends would respond to in an arts application. They provided immediate credibility among the student population.
3. Sponsor engagementBerkeley Arts+Design was committed to the success of the project, and spent a lot of time working with the student team as they refined their ideas. That partnership was invaluable, as the students learned how to respond to sponsor requirements and communicate progress. Programmatic support was also critical; the app would not have been successful without live content that was primarily developed by A+D. With those constraints and success factors in mind, here are my ideas about how to sponsor a capstone project that could actually work for your unit.
Choose a student-focused project.The team will bring their perspective as students, so they’ll begin the project with a head start. They are also more likely to be enthusiastic about an app they would personally use.
Keep your scope flexible.Part of the value of engaging with a capstone team is to tap into their creativity. If you begin with a strictly-defined scope, you will miss out on the fresh thinking that they’ll bring. (And, your scope will probably need to be rolled back because of time constraints anyway).
Participate actively.The ultimate success of any application lies in its content and programmatic support. You will need to have a staff person dedicated to working with the team during the development phase, and creating and curating new content as the app goes live. This work will probably be in addition to the person’s normal job is. And if the app is successful, that additional work may continue after the project is over. Be aware that taking on a new function will require more resources; automation never causes work to go to zero.
Find technical partners.In the campus environment, there are innumerable policies and technical requirements which the app will need to address. The A+D project required a Google Apps Special Purpose Account, a Network Registration, an Off-Site Hosting Request, a Department Security Contact, CalNet Authorization, an Accessibility Clinic, awareness of the Campus Design Guidelines, and so on. The technical bureaucracy of a place like Berkeley is difficult for a group of outsiders to comprehend. Helping navigate that stuff was a big part of my role advising the team, and CTO Bill Allison and bConnected service manager Jon Hays were important partners who kept the process moving. So, a student team really can make an app that works. We have brilliant students at Berkeley, and as a sponsor, you can help them understand how to build something that meets your needs, as long as you’re able to stay realistic and flexible. Arts+Design is super-happy with the results of the project, and is looking to use it to support an ongoing program. If you might be interested in sponsoring a Fung Institute capstone project, submit a project proposal.
‘If it works, it’s not research’: Sponsoring a successful student capstone project was originally published in Berkeley Master of Engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.