Return to Answer

Change numbered partial list to bold english text, block quote quote

edited Mar 20, 2014 at 19:47

user40980

There are two issues here, one about user centered design and the other about sprint alignment.

First, userFirst: User stories should be aligned with user needs, not just backlog. The UX stories need to have clear value to users. This does not require complete specification, and a short statement such as,

"Users will have easier access to account activity on a single page rather than divided between multiple pages"

"Users will have easier access to account activity on a single page rather than divided between multiple pages"

is amenable and adaptable to various implementations and yet still clear about the value to the user (easier access to account activity).

Sprint alignment. UX designs features in sprint X that developers implement in spring X+1. In practice, this happens in many shops and sometimes it may be more like implementation in sprint X+2 or X+3. With a tight nit and experienced team this setup can work. It becomes challenging if you have a new team or new members who are not familiar with the skill sets, preferences, habits, work styles, and tendencies of other members of the team. If you've been working together for less than 6 months this is likely to be an issue.

Second: Sprint alignment. UX designs features in sprint X that developers implement in spring X+1. In practice, this happens in many shops and sometimes it may be more like implementation in sprint X+2 or X+3. With a tight nit and experienced team this setup can work. It becomes challenging if you have a new team or new members who are not familiar with the skill sets, preferences, habits, work styles, and tendencies of other members of the team. If you've been working together for less than 6 months this is likely to be an issue.

Take a step back, and reassess. On the positive side you have the UX designers and developers working side by side, which is a boon. Start by making sure that your stories have clear value to users.

There are two issues here, one about user centered design and the other about sprint alignment.

First, user stories should be aligned with user needs, not just backlog. The UX stories need to have clear value to users. This does not require complete specification, and a short statement such as,

"Users will have easier access to account activity on a single page rather than divided between multiple pages"

is amenable and adaptable to various implementations and yet still clear about the value to the user (easier access to account activity).

Sprint alignment. UX designs features in sprint X that developers implement in spring X+1. In practice, this happens in many shops and sometimes it may be more like implementation in sprint X+2 or X+3. With a tight nit and experienced team this setup can work. It becomes challenging if you have a new team or new members who are not familiar with the skill sets, preferences, habits, work styles, and tendencies of other members of the team. If you've been working together for less than 6 months this is likely to be an issue.

Take a step back, and reassess. On the positive side you have the UX designers and developers working side by side, which is a boon. Start by making sure that your stories have clear value to users.

There are two issues here, one about user centered design and the other about sprint alignment.

First: User stories should be aligned with user needs, not just backlog. The UX stories need to have clear value to users. This does not require complete specification, and a short statement such as,

"Users will have easier access to account activity on a single page rather than divided between multiple pages"

is amenable and adaptable to various implementations and yet still clear about the value to the user (easier access to account activity).

Take a step back, and reassess. On the positive side you have the UX designers and developers working side by side, which is a boon. Start by making sure that your stories have clear value to users.

Source Link

answered Mar 20, 2014 at 19:31

atimba

There are two issues here, one about user centered design and the other about sprint alignment.

First, user stories should be aligned with user needs, not just backlog. The UX stories need to have clear value to users. This does not require complete specification, and a short statement such as,

"Users will have easier access to account activity on a single page rather than divided between multiple pages"

is amenable and adaptable to various implementations and yet still clear about the value to the user (easier access to account activity).

Sprint alignment. UX designs features in sprint X that developers implement in spring X+1. In practice, this happens in many shops and sometimes it may be more like implementation in sprint X+2 or X+3. With a tight nit and experienced team this setup can work. It becomes challenging if you have a new team or new members who are not familiar with the skill sets, preferences, habits, work styles, and tendencies of other members of the team. If you've been working together for less than 6 months this is likely to be an issue.

Take a step back, and reassess. On the positive side you have the UX designers and developers working side by side, which is a boon. Start by making sure that your stories have clear value to users.