That Old Chestnut; A 1-Sprint Project
I learned I'd be on this project last week; the client has mockups and wants to go live in two weeks.
Super doable. Super risky.
I'm writing as this happens; a live-blog of a project.
Our contract stipulates 6 templates will be functional in two weeks.
Design is provided as large breakpoint images that were made to link to each other via InVision.
Here's our website. Make it responsive.
We received an InVision prototype with a handful of pages, some, we learned they "haven't gotten to yet."
At this point, the client thinks they're getting five templates (with five release phases, where content changes and components are added/removed).
We have no ramp up; we'll be spinning up environments, hammering out design issues, and developing the front end in parallel.
I learn I have 40 hours allocated for two weeks of UX work. I'm freaking out.
On this first day of the project, our front end dev is out. The project manager wrote some stories that reflect major components or pages (good enough for a one sprint project), which we pointed.
I start breaking down the home template into responsive breakpoints, slicing in photoshop and mocking up a prototype.
What's actually going on?
My front end dev gets back from vacation and is welcomed to the project. He lets me know that we can't deliver everything we've agreed to.
We'll be cutting corners and delivering the absolute MVP.
Honestly doesn't make me feel great, but the PM assures me that if we get