Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Understanding Business Value (BV)

Any product, business or organization creates a product OR resource that has some “value”. This is the “value” that make lives easy, that produces better products, that establishes the organizations trust, vision and drive business goals.




So, how do you establish value?


A business value gives “that value” to end users and businesses to develop a “feature” withstanding the changing market needs, demands, competition and foresight. Given the focal point and decision-making stance, a business value (here after called as “BV”) became a core principle in any methodology a project/ program/ enterprise adopts or implement.


In software industry, a project is not judged by cost, number of resources nor a single intellectual SME. It’s the “BV” that is delivered in the fastest manner, iteratively and incrementally. Few Agile manifesto core team members like: Ken Schwaber, Kent Beck, Highsmith unanimously emphasize on “business value” as the core Agile principle in terms of driving the vision and goals.


And who is that person to maximize the BV?... Well, the Scrum Guide says, it is theproduct owner that steers the BV, measures ROI, drive the features in meeting the BV. Now, this realization about BV drives us towards establishing the value.


As per Scrum Guide, the Product owner is the face of the business (stakeholders, end users) who wear the hat in driving BV by understanding the strategic goals. This leads to the start of defining value, well, the meaning of value differs from every other person, project, product, organization etc. And value applies to both customer or business! Yes, the “business value” and “customer value” can be interchanged given the criteria of vision and goal defined by the stakeholder(s).


A Product Owner’s will establish and maximize the business value through strategic skills of product roadmap, product discovery, vision and tactical skills of preparing the product backlog, prioritizing, ensuring user stories are in place and well written. Meaningful techniques are employed to customize and deliver the business outcomes.


An organization will establish a BV considering these parameters in order to stay competitive and deliver value:

  • Legal

  • Stakeholders: what end users needs are and will buy.

  • Risk/ change management/ capability building: embracing marketplace and IoT.

  • Process/ service/ product: what the team is considering as excitement.

  • Cost/ market value.

Some techniques (consolidated) that maximize, measure, assess Business value at a project level, program level and enterprise levels:

  • Epic- feature-user story-tasks-estimations-Requirement Traceability matrix

  • Product backlog- slicing-Prioritization-validation

  • Empathy- personas-Stakeholder management

  • Vision/Goal-Roadmap-Release-Iteration


  • Scope-Budget (Cost analysis)- Requirements (Business, Solution, Transition)-Methodologies

  • Cost of delay-Return on investment-cash flow analysis-net present value

  • Process reengineering-SWOT-GAP-Decision Analysis

  • Sprint-Quarterly-yearly profit/loss.


As per PMBOK 6th edition, “the business value is the net quantifiable benefit derived from a business endeavor. The benefit may be tangible, intangible, or both”. The BV can be assessed through non-functional requirements:

  • Usability

  • Maintainability

  • Availability

  • Performance

  • Cycle time

  • Lead time


The BV can be assessed through tangible requirements:

  • Monetary

  • Stocks

  • Fixtures

  • Market share


The BV can be assessed through intangible requirements:

  • Brand

  • Goodwill

  • Trademarks, patents, IP

  • Reputation


Conclusion: Take any use case from your life/ working experience/ business decisions. When you start decoding the value and ROI, you involuntarily end up assessing the business value, time, estimates, market place stance, scenarios and best practices etc. etc.


If you have read this article, it's time to comment with your thoughts on:

  1. What Atlassian tools do you leverage at project level, program level and at Enterprise level?
  2. Share your use case(s) and reflections on Business Value?



Source: From my blog


Dave Liao Community Leader Nov 28, 2022

@G subramanyam - yay, scaled Agile! What Atlassian tools do you use to support scaled Agile processes?

Personally, I've used Structure to help visualize levels of work beyond the Epic > Issue > Sub-Task level that Jira traditionally supports.

Like G subramanyam likes this
G subramanyam Community Leader Nov 28, 2022

Thank you  @Dave Liao for that tool name. I heard about the usefulness and ease of using Structure app. In my previous project (pharma client) used market place app- "Big Picture( Enterprise)" for Scaling and driving the business value. This app always surprise me when comes to strategic planning at a Scale.

Like Dave Liao likes this
Dave Liao Community Leader Nov 28, 2022

@G subramanyam - how does it surprise you? I've never tried it - I've tried the older BigPicture app and have seen it used during big room planning sessions. 🙌

Like G subramanyam likes this
G subramanyam Community Leader Nov 29, 2022

Hi @Dave Liao these are few explorations from this tool which I really liked. I feel the use cases are well thought by their team.

  1. It allowed for creating "new box types" which was disabled in the earlier (parent) version.
  2. This is my favorite feature: Loaded with many pre-configured boxes to customize the organization's hierarchy (at Program and Portfolio levels), like: LeSS, SAFe ART, Agile, Hybrid project etc..etc.. which is very huge. The parent version seems to have only 3 boxes like-Program Increment (SAFe), Program, Iteration.
  3. It allowed to create "multiple alternate scenarios in Live mode".
  4. Workload contouring to understand/ decide and distribute the tasks in the specified time.
Like Dave Liao likes this


Log in or Sign up to comment

Atlassian Community Events