Working Hard to Solve a Problem That Does Not Exist.

( Credit : EnJoy It) 

Here is a good & hilarious example of working hard to solve a problem that does not exist.
Do you see a similar kind of hard work around you?
Well, I do.

Here are a few examples of solving non-existent problems from the "A"gile circle...

• Doing an endless comparison between various frameworks and nailing down every minutest difference between any two. (An indication that Org wants to be a passenger on the bandwagon. This could also be an indication that the stakeholders do not have a common agreement on the End-Objective) 
  
  
• Investing huge energy & time to do better and better Estimation. 
  
  
• Measuring Velocity. (A clear sign of celebrating Effort, rather than Outcomes)
  
  
• Trying to maintain steady Velocity (Completely a wrong ambition)
  
  
• Obsession with Capacity Planning & endlessly searching  for “THE BEST” template for Capacity Planning
  
  
• Working hard to invent novel ways to “Add Fun”, particularly in Retrospective
  
  
• Seeking more and more ways to do self-assessment of team's  "A"gile Maturity
  
  

In all these cases, the intentions are not bad. 
But having bad intentions is not a must to go on the wrong path.

How to focus on problems that are worth solving?
Well, one approach could be...
Laser sharp focus on the market and having an outside-in view.  Laser-sharp focus on the market could lead to: 

• Gathering market feedback frequently 
• Finding out & doing THAT piece of work that would generate maximum RoI
• Releasing in shorter cycles, (at least building & showcasing in shorter cycles)
• Working with thin slices, which would enable showcasing in shorter cycles
• Working with thin slices, which would safeguard us from generating big waste

All these problems are worth working on. And when you work on them, it creates +ve impact on business. 
Business of the Customer as well as yours.