Help Defining a Story

[Gregg Bolinger]

I sometimes still struggle with how certain stories should be structured or if they are supposed to be stories at all. I'm stumped again on the following:

Our design team has been busy implementing some new screens. Some of these screens are improvements to existing. Some are new. It is now time that we take these designs and wire them into the backend so they actually do something besides look pretty. So what are the stories that would encompass doing the wiring? For example, we have a few screens that deal with a customers account information (name, addresses, etc). All those screens were already there, just in a slightly different state/location. Now that they have been moved and improved, there is some wiring to do on the back end.

A story like "As a user I want to be able to manage my mailing addresses" is not right because, technically, they can do that now. So I'm a bit lost on what the story should be for that. One possibility that I am playing around with is:

"As a system I need to be wired to the new customer account mailing address designs"