Demonstrating progress was easy In the old days, when I would work on a website project, there were some natural phases to the work I did. Your process may have been different, but mine went something like this. Phase One: Define project / Agree on Scope Phase Two: Create Thumbnails of Design Concepts Phase Three: Create Photoshop Files of Final Design Phase Four: Turn Designs into Code Phase Five: Fine Tune Everything Phase Six: Launch If this feels very “waterfall” to you, and you’re more of an “agile” person, know this: I did a lot of iterating in each phase with customers until they were happy. Does this sound familiar? I’m ok if you had a slightly different approach. But I’m guessing it was more similar than dissimilar. And it used to really work. How did people understand progress? Well, once I laid out how things were going to go, they understood both the process and the deliverables they would expect. They’d get a scope document, wireframes, design files and then there would be a bit of quiet during the coding part, and then they’d see everything. Did you catch that? There would be a tiny phase of silence in stage four where
Share This