This site uses tracking cookies. By using this site, you agree to our Privacy Policy. If you don't opt in, some parts of the site might not function.
Blog
Home / Blog / FileMaker / Project Estimation Best Practices: A Look at Our Three-Point Estimator
31Oct 2018

Project Estimation Best Practices: A Look at Our Three-Point Estimator

About the Author

Steve Lane Steve Lane

Steve is Soliant's Chief Technology Officer and has been working in the areas of databases and software development for over twenty years. From a background in academics and higher education, he moved into the technology industry and has been leading software teams for the last dozen years or so, working with hundreds of clients of all sizes. He is a recipient of the FileMaker Excellence award and has co-authored six books on database development. After graduating magna cum laude from Yale College, Steve earned a master's degree and Ph.D. in history from the University of Chicago, as well as an M.S. In Computer Science from the same university.

Comments (2)

Therese - January 3, 2019

Hi Steve,

I very much enjoyed your blog post! Do you ever circle back at the end of projects and compare actual hours/cost to estimates? How well does the method predict the final hours/cost? And if you do go back and compare, how do you filter out the hours added by “scope creep”?

Reply
    Steve Lane
    Steve Lane - January 14, 2019

    Hi Therese — sorry for the slow reply, I was on vacation the first half of January. The short answer is that, while we do compare estimates and actuals it’s never apples to apples, because the project always changes as you build it, so the project the customer wants at the end is not the one they wanted at the beginning. That said, the way we do our tracking now, we do know how much work got added and can figure out what was original and what was new. Good topic for another blog post!

Leave a Reply