Skip to main content

Tracking project revenue in Scrum way using JIRA

Tracking project revenue in Scrum helps project manager to monitor and forecast the project.


As a manager you will be closely working with Sales team and Finance team for creating SOW.

You should have the job level rate card for the project as below and calculate the Blended Rate ($/hr).

In this revenue calculation we are running project in Scrum and using JIRA tool. 


Blended Rate = average of all above Rate.

Please note down below formula for find the project running in positive revenue or running in negative revenue.

Planned Cost = Planned Hours*Blended Rate

Planned Margin = (Planned Revenue-Planned Cost)/Planned Revenue*100

Actual Cost = Actual Hours*Blended Rate

Planned Margin = (Planned Revenue-Planned Cost)/Planned Revenue*100

Actual Margin = (Planned Revenue-Actual Cost)/Planned Revenue*100

Delta = Actual Margin - Planned Margin

When Delta is Positive value the project running with Positive margin and when Delta value is negative the project running with Negative Margin.

Important Note: The above decision need to be considered based on the % of task completion. For example in the first example (JIRA-123) Delta value is positive but the % of task is 50% instead of 100% then the we need consider this as negative margin. The status need to tracked during daily stand up.

Use below fields in JIRA for tracking time:

  • Original Estimate 
  • Remaining Estimate


 

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

Voice of the Customer (VoC) vs Voice of the Business (VoB)

  Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...
Post a Comment
Read more

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)
Post a Comment
Read more