As a contribution to consider software projects to be risk investments, it is important the full standardization of either the planning methodology (as a subset of project management methodology) and the effort estimation method. We think there is important and abundant evidence backing the convenience of the join use of Project Management Body of Knowledge and “Use case points” method in software project planning and control. Software development teams should share information, as it is important to compare the “ex post” analysis of programming/budgeting estimations against project execution data with “real world” software projects. This comparative activity would include teams into a permanent improvement process.