Design first (incl. client approval)
psd file deliverable for developers
expected pixelperfect layout in all browsers
linear workflow (concept + design, development, testing, etc.)
developers not involved from the beginning
e.g. Bootstrap as the tool to "just get responsive design done"
"go mobile" after launch of desktop-site
"desktop first" design
only support e.g. iPad, but also IE8 ... !? What about these:
"unforseen problems" happen during development
over-time, over-budget, performance lacks,
bad maintainability of code
complementary teams: concept + designer + dev
always think mobile first & use progressive enhancement
no photoshop deliverable (for devs)
modular design elements, no full page layouts
build prototypes - in the browser
get client sign-off for new deliverables
replace slow mobile / desktop sites
first focus on "mobile" experience
one code-base, one responsive site
or what to do before development starts
"Before setting out on a large responsive journey, I recommend writing a very short document, agreed upon as a pact (of sorts), the content of which should be agreed upon by all the ‘chiefs of staff’.
Briefly define why this responsive project is being undertaken. What does each party/stakeholder hope the benefits are of completing the project (easier feature development, less development time, reduced support etc).
When things get fraught and ugly (they often do), this is the document to which you can all refer back to, and remember why you set off on the journey in the first place.
Really large responsive builds often take more than a year, and should personnel come and go in that time, this single page document will also serve as the manifesto for your project.
Example from Velux project
documented element from design styleguide
automatically updated frontend styleguide