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

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Lessons learned in Project Management

Lessons learned in Project Management Lessons learned (it may be +ve or -ve) in project management are the knowledge gained during a project that can be used to improve future performance. Lessons learned are documented with solutions to provide future project teams with information that can increase effectiveness and efficiency. Every project manager should be well aware of the impact lessons learned can have on the current and future projects. However, despite knowing the value of lessons learned, not everyone makes full use of them.  The lessons learnt documented using below process flow: 1) Identify: Identify comments and recommendations for use in future project. This is usually done through a project survey that is sent out to all team members. Various questions connected to a project help the participants share their lessons learned.  2) Document: Document and share the findings 3) Analyze: Analyze the finding and find the solution 4) Store: Store in a repository 5) Ret...
Post a Comment
Read more