Our work doesn't speak for itself, says Austin Kleon. In this project, you'll work with your book project teams to create the story of your team's DPS App or Atlas project. Your case study eventually should be presented (and presentable) in multimedia formats including text, audio, video, and other forms of interactive media. Your audience for this project will be book publishers, industry specialists, Clemson faculty, students, and staff, and the wider public. Each collaborative group will be responsible for producing a case study documenting its component of the larger project and the results.
Because both platforms are new technologies designed to solve a real world problems, you'll need to do some background research on the applications and how they may have been used by others (including interviews). Your finished case study will tell the story of how you approached these problems or challenges and the steps along the way and your decisions as you addressed them. There should be two main components of the finished case study: 1) ~5-minute video; 2) print- and web-based document with visual, aural, and animated content embedded in text. Together, the case study components will provide background information on the problem or challenge, a description of the current challenge and your goals, a detailed overview (supported by visual content and verbal content) of the steps taken to address the challenge or achieve the goal, and then a discussion of how well your solution has worked. You'll be asked to complete a Collaborative Project Evaluation Form at the end of the project. (Collaborative; 20% of course grade.)
Working with your major collaborative project team, tell the story of your work with the DPS App or Atlas platform. Because there are two teams in each category, you'll want to divide responsibilities for each part of the final package. Use Adobe Story to organize your project(s). The length of your case study should be about 2,000-3,000 words (more or less), not counting images, screenshots, illustrations, audio, and video. Each "chapter" of your story should have descriptive headers, every image/video/sound clip should have captions, and you should document all citations with a references section at the end. You will also likely link to similar work by others. Use the examples below to inspire your work. Be creative and innovative, and (if at all possible) have some fun. If you can tell a great story, you'll be asked to tell it again and again!
These examples include both images and text in good proportion, and each describes the successful application of some technology to solve a problem or achieve a goal. Some of them are longer than yours may need to be, and some much more technical, but they will still give you a good sense of the genre. Notice how the writers articulate problems and then show you how they approached solving them.
Mobile Media Production (School of Journalism and Comm, Univ. of Oregon; 5 min. video)
Drupal Case Studies (Website development; entrepreneurship; lots to choose from; about the right length)
Case Study: Find Your Way to Oz (computer game development; highly detailed)
Seven Creative Social Media Marketing Mini Case Studies (short, but well presented)
Social Media Examiner (lots of great ones here, so just pick a topic you like; hese are like "how-to" guides in some cases).
Startup Company Eliminates the Cold Call With Twitter (at Social Media Examiner)
Steps in the Process
1. Focus. Atlas and DPS App teams should discuss and then apportion the various responsiblities for the completed case study, appoint team leaders and other responsibilities, and create the project in Adobe Story.
2. Research. Find out everything there is to know about your topic:
- Read any existing company or organizational documents relevant to your topic.
- If possible, write some interview questions and ask someone in the organization (Clemson, Adobe, Atlas/O'Reilly) if he or she would be willing to answer them briefly. Important: Follow these Ethical Guidelines for Conducting an Interview with a Client. You should talk with Dr. B before contacting anyone and only after formulating your interview plan carefully.
In your team's weekly blog post, you should assemble and report on your research. Some content can be stored in your team's Creative Cloud shared folder(s).
3. Collect Assets. As with the documentation project, you'll need images, video, audio, screenshots and more for your project, ones that you create yourself (with a camera or screencapture software) or that you use from other sources. If you use images from another source, you must have permission to use it in your project, which means that you'll want to use Creative Commons licensed, public domain, or royalty-free content. Here's a page with Sources for Photos, Illustration, and Content. The collection of assets will start on day 1 and continue throughout the project.
- Asset Collection: Using authentic content, produce samples and screenshots that you'll use later to illustrate key parts of your case study.
- Screen capture: (Repeated from the documentation project): Install the Google Chrome browser add-on for making screenshots. Try "Screen Capture" by Google or "Awesome Screenshot: Capture and Annotate" by Diigo. Practice using it to create annotated images. Or use GrabIt (a pre-installed app in Mac OS) or check out this list at The Best Screen Capture Tool for Windows at LifeHacker.
- Create your team's Creative Cloud folder to store your team's assets and share the folder with team members and Dr. B. (Be sure to give it a name that clearly identifies what it is and who owns the folder, e.g., DPS App Video Team Assets.) Some assets can be included in or linked to from Adobe Story.
4. Plan and Compose Your Case Study. Rough drafts due April 7; Full drafts due by April 21.
- Your team will need to decide, based on all the examples and possibilities, the best method for presenting a first-class case study project.
- Your final document(s) and deliverables should submitted via a "Case Study Deliverables" folder in either the DPS App or Atlas teeam folders. Your project submissions should consist of a single PDF document or (if you use another media for your presentation, such as HTML) a folder with supporting files, images, etc.
5. Progress Reports. Plan on presenting these weekly, starting Week 8.
Please complete the Collaborative Project Evaluation Form at the end of the project and submit it to Dr. Blakesley separately by email no later than April 28, 2015.
Your project will be graded based on the quality, documentary accuracy, and creativity of your case study, as well as its presentation and usability for multiple audiences. You are expected to be a good collaborator, someone willing to do his or her share and to make sure that everyone is involved and productive. You must complete all steps in the process on time, including the collaborative evaluation form, to earn a passing grade on the project. The project counts for 20% of your course grade.