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


 

Comments

Popular posts from this blog

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

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .