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

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...

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

High-Tech Yuga

Search This Blog