Building documentation for a web or mobile project the right way

Evan Kimbrell, Director at Sprintkick

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
11 Videos (1h 17m)
    • Welcome to the class!

    • First thing to do

    • Creating an overview

    • Creating a functions list

    • Example of creating a functions list

    • Adding pages

    • Adding the user section

    • Adding parameters

    • Adding comments

    • The class project

    • Keep the learning going


About This Class

9/10 people who write specifications and documentations for their web or mobile projects do it wrong. They don't add enough detail, they forget crucial sections, or they use confusing standards resulting in unforeseen amounts of lost money, time, and human resources.

Don't be one of those people. Learn how to effectively document your projects so that all parties - not just developers and designers - can understand.

In this class, we're going to go over documentation and specifications. We're going to go from the Project Manager's viewpoint and tackle how to capture all of the relevant information from your project onto a set of pages.

We're going to cover the written aspect of documentation, but may I add that I highly suggest you learn how to add wireframes, which are just as important as the text itself.

What you'll learn:

  • What sections you need to include for any design or development project.
  • How to accurately put together an overview statement to get your team members on the same page.
  • How to list out and revise function lists.
  • How to tackle the task of listing pages and which areas are most commonly forgotten.
  • The correct way to comment and annotate.
  • Adding user personas and user goals as an addendum to your specs.
  • Adding parameters to tackle functions that need further explanation.

What you'll do:

At the end of the class, we'll work on creating custom documentation for your project (or any generic project you want to practice on). You'll follow the steps we followed in the class, post it to the group, and receive direct feedback. Remember: Practice makes perfect.

6 of 6 students recommendSee All

This is actually important and often overlooked. When i started, i have no idea how to write a proposal to forward to my clients and development team. Though now i don't claim to be an expert, at least i have a better idea of the structure, what to include, what not to include, in the proposal document. Evan does not need to be so detailed in the explanations but he does so anyway, so people can have a better idea but others may find it long-winded. Overall, i learned some new things and this class is worth sharing.
Very informative class! Every step is explained in details, you just have to adapt it to your own projects.
This guide really helped me put together all the details of my project. I believe it's the best way to eliminate possible misunderstandings between you and your developer.





Evan Kimbrell

Director at Sprintkick

Hi, I'm Evan Kimbrell.

Thanks for checking out my classes.

Currently, I'm the Founder, Director of Sprintkick, a referral-based full service digital agency based out of San Francisco. Over the past 4 years, I've overseen the development and launch of over 100 web and mobile apps. Clients range from 1-2 man startups bootstrapping their initial idea to multibillion dollar Fortune 100's like Wal-Mart, Dick's Sporting Goods, & GNC.

Prior to Sprintkick, I worked as a VC for a firm called Juvo Capital, based out of L.A. I spearheaded the firm's expansion into the Silicon Valley deal flow and into the Consumer Web tech category.

Before working for Juvo, in the long, long ago, I was a co-founder for an educational software startup called ScholarPRO that raised a ton of money and then spectacularly blew up (in the bad way). Before it exploded like the Death Star, I went through 5 tech incubators (yes 5) with Tech Stars, Excelerate Labs, MassChallenge, Babson Venture Program, and Sparkseed.

That's enough about me. Hope you enjoy my class!