By:  Jim Downs The term “values” is overused and frequently misused in business today. While values are certainly crucial to any company, too many organizations today spend more time talking about their values than making sure they are actually living them. We recently published our values on our website, and as such, I wanted to
Read more »...

Philosophy 5: Decline projects when the client can’t grasp the concept of iterative releases (no big bangs) Some of our potential clients want to give us a fully specified project to undertake, where the expectation is that we build to that specification and deliver in one big bang a finished product.   When we see
Read more »...

Philosophy 4: Identify and explain project risks to the client before accepting a project All software projects entails risk. Be it a ground up custom build, an implementation of an “off-the-shelf” product for a customer, a modification of existing software, or a rebuild of a legacy system (make it do this — just better).  
Read more »...

Philosophy 3: Only accept projects where there is a clear understanding and agreement of the features of the software to be delivered This seems obvious. However, you might be surprised at how many software projects are started where the developer and the client have very different ideas of what the finished project will be.  
Read more »...