Painfully-funny and yet it happens all the time.
Defining the client’s specifications for a project, design, or a product well will save you tons of hassle down the road.
Right?
Do you have a defined process for this? What do you typically do?
The #1 Resource for Church Technology Creativity & New Thinking
Painfully-funny and yet it happens all the time.
Defining the client’s specifications for a project, design, or a product well will save you tons of hassle down the road.
Right?
Do you have a defined process for this? What do you typically do?
Free resources, top posts, and more!
[…] This post was mentioned on Twitter by 8Bit, ChurchCreate. ChurchCreate said: Wally Does Client Spec [Comic] http://bit.ly/bBOcy5 […]
oschurch says
It’s always good to get up front info from the customer, but never think that the customer really knows what they want…or maybe knows how to really express what the really want. Many times it really does sound like “lion’s pecs” until you’re closer to the end. If you can’t tell, I’m a fan of agile development and not just for software development. 🙂 My experience with it is that it takes a while before people really get it and can function well with it. However, once that price has been paid it is a much more efficient and effective way to gather client info and execute on it so that the final product has value.
Kevin
http://opensourcechurch.com
Chris says
Great points, Kevin!
peace | dewde