For those not seeing the sense in this change, keep in mind that many teams have adopted a Product approach vs a Project approach to work, especially when they will continue enhancing their product indefinitely into the future. Calling those collections of work "projects" was always weird, and this fixes that problem. "Product backlog" is a more common term outside of Jira vernacular, but "Space" is generic enough to work for both Product- and Project-oriented bodies of work.
So I'm pretty happy about this change. I assume lots of others are too but just aren't commenting here.
@Jeff Madison it isn't that we don't see the sense in the change, it is just that we do not agree with it. What you described is exactly the scenario I explained in a previous comment about changing the tool because it of "how we use it". Just because there are some people that purchased a Project Management tool and don't like that it is using the term Project does not mean it should be changed to accommodate that.
I will ask again, why can it not be a new added feature to accommodate the cases where people are wanting to not call a project a project (and yes, I understand what you stated, but I do not agree, as a long standing project is still a project)?
I also do not think using the term "Product" is correct as a product is something that is provided from one entity to another, either as a physical or virtual item, or as a service. We do not work on software development products, we work on software development projects to create products.
103 comments