Unlike ultimate car builds, radical chopper assembly, building a house, paving a road, and other similarly natured projects — software development projects are one of the most challenging, difficult, and yet exciting types to be a part of.
In the ideal world of webshop development projects, you start off with the usual steps of:
- speaking with the client
- clearly understanding what they need
- creating a properly written scope of how you as a project manager understand their needs
- submit these documents to the client for review and approval
- coordinating with your design team so they can create design proposals
- discussing those design proposals with your client
- a bit of lull time (maybe a few minutes in between projects, haha)
- client comes back with design suggestions of his own
- design team implements those suggestions and you resubmit that to the client
- client approves… a “go ahead” is received for development
- design team cuts and creates html guides
- then the development team takes over….
- development days are earmarked by end-of-day checkpoints…
- as weeks go by… an alpha version is setup on a staging server (still strictly according to scope) … or so you thought
- as the alpha version is updated to beta, the client is allowed to go in and see the product
- the client likes what they see (that’s a day into the runthrough….)
- then comes the dreaded… EMAIL!
- wham, then all hell breaks lose
- the tides of thundra run dry and the clouds burst with lightning…
- days become 16-hour chunks of energy-consuming globs…
- …shall I go on?!
I love my profession, but sometimes, the art of turning out and delivering a lock-stock-and-packaged software is a goal too hard to accomplish, especially when some clients can change minds faster than they change lanes on a highway.
… and these situations can obviously end in many, many ways.