Skip to main content

Planned Value (PV) and Earned Value (EV)

 Budget at Completion (BAC) is the total estimated cost of a project after it's completed, including all allocated budgets and any remaining budget. It's a key factor in client project planning, helping to understand the total expected expenses. BAC is established early in the contract at the control account level and can be rolled up and reported at any level of the Work Breakdown Structure (WBS).

Planned Value = (Planned % Complete) X BAC (Budget at Completion)

Example:

Project cost (BAC): 100,000 USD

Project duration: 12 months

Time elapsed: 6 months

Percent complete: 50% (as per the schedule)

= 50% of BAC

= 50% of 100,000

= (50/100) X 100,000

= 50,000 USD

Therefore, the project’s Planned Value (PV) is 50,000 USD.


Earned Value = % of completed work X BAC (Budget at Completion)

Example:

Project cost (BAC): 100,000 USD

Project duration: 12 months

Time elapsed: 6 months

Percent complete: 40% (as per current status)

= 40% of BAC

= 40% of 100,000

= (40/100) X 100,000

= 40,000 USD

Therefore, the project’s Earned Value (EV) is 40,000 USD.

If the project going in same trend it will take 3 months additional timeline to complete the project.

 


There is no special formula to calculate the Actual Cost. It is an amount that has been spent, and you can find it easily in the question.

Example of Actual Cost (AC)

You have a project to be completed in 12 months. The budget of the project is 100,000 USD. 

Six months have passed, and 60,000 USD has been spent, but on closer review, you find that only 40% of the work has been completed so far.

The Actual Cost is the amount of money that you have spent so far. You have spent 60,000 USD on the project so far.

Hence,

The project’s Actual Cost is 60,000 USD. 

Comments

Post a Comment

Popular posts from this blog

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Bucket System project estimation

 The Bucket System is an Agile estimation technique that uses predefined buckets to group tasks or user stories by size, complexity, or effort.  Each bucket represents an estimate range, such as small, medium, or large.  The Bucket System is a group activity that helps align the team's understanding of work effort and complexity.  It's a good technique for quickly estimating a large number of items with a medium to large group of people. The effort of small, medium, or large bucket size arrived by team based on T-shirt sizing, PERT estimation or Planning Poker. Each bucket represents a level or an estimate range (e.g., small, medium, large). The team compares user stories to one another and places them into the appropriate buckets. This process is a group activity, promoting discussions and aligning the team's understanding of work complexity and effort. To use the Bucket System: Set up a row of cards, or buckets, with values in the Fibonacci sequence or other metho...
Post a Comment
Read more