Project Workflow
A blueprint of a website project workflow in our agency.
Plan [p0]
This phase usually starts directly after client approves our proposal.
Project kick off (30')
define responsibilities and teams
get a common understanding of scope, requirements and constraints of the project
balance out volume, timing and deadlines of the single project phases
Research [p1]
This phase is optional, and can often be skipped, as it rarely is the subject of a presentation.
Sometimes it's needed to kick off creativity
Design Concept [p2]
In this phase we're usually breeding out our concept(s).
At the end we present concepts to the client
Concept kick off (30')
Define the shape of the concept phase (how many concepts? how many screens?)
Define the deliverables of the concept phase (screenshots?, slideshow?, animation?, mockup?, wireframe?)
Concept creation (x')
creative ideation, only project scope and constraints are the limits
somebody of code-unit should be there as well to prevent costly "fantasy"-features that will push the implementation work on the project out of scope
preparation of deliverables
Design Development [p3]
Detail work after the client decides for a concept.
Often there is back-and-forth with the client and refinements are happening.
We try to use tools that allow for rapid iterations.
Design system and components (30')
how can the website be designed with the minimum amount of individual page types/components
layout grid?
design system?
breakpoints -vs- fluid layout?
Design work (x')
design fun
preparation of deliverables
Implementation [p4]
Architecture workshop
Kicks off the technical implementation of the project.
structure and content (15')
what is the node structure of the website?
which part of the structure is predefined, which part is dynamic (client managed)?
define content mock-up vs. real content
modularisation (60')
define all initial views/page types
define a naming scheme for the page types
split pages into presenters
define names for presenters
which existing plugins/components that could be used?
presenter configurability (variations) -vs- single presenters
should presenters be split further into components?
define names for "components"
what's the implementation method for each component (traits, inheritance, foreign presenter hooks)
[ideally create a component scheme] <-> [or probably already mock it up in ff]?
web platform considerations (45')
define a layout strategy
define semantic html structure
which scripts will be needed?
logic (45')
define specific features, that we don't have in our toolbox and add a rough price tag to them
where does the logic happen? in presenter?, in separate class?, in a separate plugin?, elsewhere?
define data mapping (metadata -vs- text -vs- attributes)
define in which parts of the project we need content management ui
implementation plan (30')
who does what? (assets, html, css, js)
write down tasks with a rough effort estimation
prioritization of implementation plan (what comes first, what is nice-to-have)
definition of SEO optimisation
definition of milestones and deadlines
Coding work
setup (15')
set up a ff instance with needed plugins
set up project plugin(s)
set up a git repo for the project, excluding content, cache and logs
customise initial settings
set up admin and author users with specific passwords
code (x')
work towards defined milestones
check off your tasks
use the "30-minute-rule" (if you hit a wall for > 30 minutes, ask a colleague!)
git commits based on finished tasks
Maintenance [p5]
staging & launch
update plan
after sales