Getting right to the point, many (possibly even most) software/web developers will simply hand you the deliverable upon project completion and call it a day. The tools and processes used are often held back, forcing you to always go through them for updates or eventually argue with them to get what you need. Although the former may make a bit of business sense on the consultant’s side, I’d argue that this methodology is terrible. Continue reading The Responsible Consultant: What project information should my software/web developer provide?
This morning, I stumbled across this blog post, describing “Good Consultants vs. Bad Consultants”. Although it’s a little rough around the edges, the points it makes are important. Continue reading Define: Good Consultants