The backlog forecasting has been a topic of contention among my sprinting and kanban teams.

Problem: When a user looks at the backlog in the team room, the forecast appears as if this is the actual plan. Since the organization is adaptive and emergent, the work does change frequently based on researching and testing. The items are broken down into small digestible pieces under a main strategic idea (epic). The new work emerges daily but still contributes to the main objective that has been committed to. The system forecasts the information in a way that is not relevant to how the team actually works.

Solution: There are most likely many ways to handle this problem. The easiest way is to implement this would probably be to have an option in the teamroom properties to turn this feature on or off.