Scrum provides "Big Visible Business Value"

In John Johnson's post entitled Big Visible Business Value, he makes some interesting points regarding the problem of always seeing both your immediate goals and the big picture.

"It strikes me that we pay a lot of attention to business value when kicking off a project. We may directly look at the business case and the key business drivers. We will use this information in our prioritization, scoping, and initial release planning. And then we put this information in a jar marked 'Steering Committee' and—for the rest of the project team—that’s the last we really hear about it."

"Part of kicking off a project, or a new release (or even an iteration) should be to define the priorities...each release could have one; even each iteration. Working as an integrated high-performing team means having common priorities, but if we don’t know the priorities—or what really matters—then how can we achieve this state?"

I couldn't agree with John more. In fact, I have the solution. Solving this problem is one of Scrum's biggest strengths.