Skip to main content
Software Engineering

Return to Answer

added 1 characters in body; added 8 characters in body
Source Link
RationalGeek
RationalGeek
  • 10.1k
  • 7
  • 39
  • 56

Who does UX on a waterfall project? Who does mainframe development on an XP project?

The project methodology doesn't matter. Every technology project requires certain specialized roleroles. Sometimes, a project can get away without a fully licensed and bonded "interaction designer" (whatever that means). Sometimes you do need someone that specialized. But the same could be said for every other role.

So onto your second question of how you deliver high quality user experience using agile. We managed it in the last scrum project I was involved with by involving the business analyst and the customer early and often. Also, we had a developer that had a particularly good eye for UX. He tended to make minor tweaks to the UIs the devs were working on after they had done commits.

We didn't deliver itperfect UX at the end of every sprint. The demos generally exposed an issue or two from a UX perspective. But we fixed those for the next sprint (if they were worth it to the customer) and by the time we released to production we had a very solid UX.

Who does UX on a waterfall project? Who does mainframe development on an XP project?

The project methodology doesn't matter. Every technology project requires certain specialized role. Sometimes, a project can get away without a fully licensed and bonded "interaction designer" (whatever that means). Sometimes you do need someone that specialized. But the same could be said for every other role.

So onto your second question of how you deliver high quality user experience using agile. We managed it in the last scrum project I was involved with by involving the business analyst and the customer early and often. Also, we had a developer that had a particularly good eye for UX. He tended to make minor tweaks to the UIs the devs were working on after they had done commits.

We didn't deliver it at the end of every sprint. The demos generally exposed an issue or two from a UX perspective. But we fixed those for the next sprint (if they were worth it to the customer) and by the time we released to production we had a very solid UX.

Who does UX on a waterfall project? Who does mainframe development on an XP project?

The project methodology doesn't matter. Every technology project requires certain specialized roles. Sometimes, a project can get away without a fully licensed and bonded "interaction designer" (whatever that means). Sometimes you do need someone that specialized. But the same could be said for every other role.

So onto your second question of how you deliver high quality user experience using agile. We managed it in the last scrum project I was involved with by involving the business analyst and the customer early and often. Also, we had a developer that had a particularly good eye for UX. He tended to make minor tweaks to the UIs the devs were working on after they had done commits.

We didn't deliver perfect UX at the end of every sprint. The demos generally exposed an issue or two from a UX perspective. But we fixed those for the next sprint (if they were worth it to the customer) and by the time we released to production we had a very solid UX.

Source Link
RationalGeek
RationalGeek
  • 10.1k
  • 7
  • 39
  • 56

Who does UX on a waterfall project? Who does mainframe development on an XP project?

The project methodology doesn't matter. Every technology project requires certain specialized role. Sometimes, a project can get away without a fully licensed and bonded "interaction designer" (whatever that means). Sometimes you do need someone that specialized. But the same could be said for every other role.

So onto your second question of how you deliver high quality user experience using agile. We managed it in the last scrum project I was involved with by involving the business analyst and the customer early and often. Also, we had a developer that had a particularly good eye for UX. He tended to make minor tweaks to the UIs the devs were working on after they had done commits.

We didn't deliver it at the end of every sprint. The demos generally exposed an issue or two from a UX perspective. But we fixed those for the next sprint (if they were worth it to the customer) and by the time we released to production we had a very solid UX.