As your Product Team developed JPD, how did you track the cost?

[Carolyn McNicoll]

One major challenge organizations have with working in agile ways is understanding the cost.  Every large organization I've worked with struggles to let go of the old project management budget tracking.  One reason for this is they won't reorganize the company into collaborative cross functional teams that are able to deliver without handoffs to other teams.  And they don't revisit their accounting practices or strategy and planning methods that also need to learn from the agile ways of working.  

Tanguy Crusson mentioned in his JPD videos that you work in cross-functional autonomous teams.  With the focus on Product and Outcomes, do you track the cost by Outcome?  Is it a simple equation of Monthly team cost * number of months to do the work, from Idea to Delivery (Wonder to Impact)?  

It would be great if via the Atlassian tools, with JPD and Atlas/Home we could enable simplified planning and cost calculations.  Similar to how you've shared the JPD journey, working with customers, and building off the feedback loop, then providing the JPD Handbook, it would be beneficial to help companies learn how to do continuous planning by product outcomes and then wrap it up with the cost per product outcome.  

No more quarterly planning (that is changed hours after decisions are made) and no more financial gymnastics chasing dollars and hours by person trying to determine the project cost.