Estimates are the cornerstone of completion for any project and always a challenging item on a project to address. One of the main reasons it is so difficult to work with estimates is that they are often put together under duress of a predefined timeline. This paper reviews a case study as an opportunity to define a clear approach for estimations on software development projects. The method discussed is the combination of two approaches previously put forward. The first is a straight-ahead approach of using specific estimations for specific goals. The second approach modifies the first in regards to the information you have on the activities.