How are cosmetic improvements / changes handled?
Hi all, so we have a current app where we, every now and then, do some cosmetic improvements in texts, titles, sometimes images, etc. and I was wondering how are those supposed to get into the backlog? Sometimes, as an example, we add a new feature for the app and we need to adjust the Welcome screen to include the name of the new app in a existing paragraph. Some other times we just need to improve the text of an existing title on a given screen.
Right now we are creating a user story (Because are not defects), but I was wondering if that is the right way. If I look at it from the "business value" perspective, there are none really but are improvements we like to do.
Thanks
The Product Backlog is the emergent, ordered list of all changes needed to improve the product. Although the Product Owner is accountable for creating and communicating Product Backlog Items, they can delegate this to others. The people who add Product Backlog Items vary by team and organization.
The use of any of the various story types and formats are complementary practices. The Scrum framework doesn't offer any specifics as to how to structure Product Backlog Items. Using more traditional user story formats, like the Connextra format, are up to the team and may not be appropriate for all types of product changes.
Right now we are creating a user story (Because are not defects), but I was wondering if that is the right way. If I look at it from the "business value" perspective, there are none really but are improvements we like to do.
Does the Product Owner think it's worth doing? Can he or she order it on the Product Backlog in relation to other items and account for its value?
If not, do the Developers believe it needs doing in order to ensure the product quality they are accountable for?
If I look at it from the "business value" perspective, there are none really but are improvements we like to do.
I'd argue that there is business value in them. Maintaining your brand, directing people's attention to new features, clarifying instructions or statements all have value. It may not be as big as introducing new functionality, but there is still value. Otherwise, why would you do it?