UX as Core to Product delivery

Question 1

Which of the following describes bad Agile UX practices:

a. Dev and UX teams have equal power and participation in design decisions
b. Dev teams have the final say in design decisions
c. Field research is conducted early on (Cycle Zero)
Submit your answer

Answer 1

Field research is conducted early on (Cycle Zero)
Submit your answer

Question 2

What are examples of Good Agile UX?

Answer 2

1. Field research as cycle Zero!
2. Solutions to dev just in time.
3. Validating product requirements
4. Helping product owners stay grounded with MVP decisions.
5. Designs are generated collaboratively.
6. Testing is happening bi-monthly at least.

Question 3

What are examples of Bad Agile UX?

Answer 3

1. No time for testing!
2. UX team left out of: Stand-ups, Backlog, Sprints, and Retrospectives).

Question 4

What are examples of Bad Agile UX?

Answer 4

1. No time for testing!
2. UX team left out of Stand-ups, Backlog, Sprints, and Retrospectives).

Question 5

What is the problem with a pure MVP approach?

a. It can focus on what’s not so important to the business
b. It can lead to decisions that interfere with the user experience
c. It can lead to reactive development that does not include user testing

Answer 5

b. It can lead to decisions that interfere with the user experience

the issue with MVP is that you can get very narrow; you can get very niched into a discussion about what makes something viable. But you should remember usable. You should remember desirable. Right? Viability comes from maximizing what you can from UX. And decisions ultimately need to be made in conjunction with UX, technical and business opportunities combined.

UX is not something that you just do at the end. It’s not something that comes in later, later on. You don’t make all the grown-up decisions and then UX is the child that throws the paint at the canvas. That’s not what UX is. UX is critical to technical and business decisions. And anyone who doesn’t understand that is just projecting a technical bias onto software development.

Question 6

MVP is also called in the UX world …

Answer 6

Minimal USABLE product
Minimal DESIRABLE product

*Viable should come from where UX can get the biggest bang!

Decisions should be made in conjunction with Technical + Business and UX opportunities.

Question 7

What is a good way to think about Agile and UX working together?

a. Rules are set out by UX teams, and Agile teams are encouraged to follow them

b. Rules are set out by the agile team, and UX teams are encouraged to follow them

c. Rules and behaviors for developing and designing the software and UX are followed by the dev and UX teams

Answer 7

c. Rules and behaviors for developing and designing the software and UX are followed by the dev and UX teams

One of the relationship rules between UX and Agile is to implement processes where developers and designers will work on and co-benefit.

Question 8

Marry Agile + UX Culterually (Rules)

Answer 8

1. Culture is defined by rules and behaviors
2. It requires a combined commitment and evangelism from Top roots and Grassroots parties.
3. Get Agile UX coaching and implement dev and UX processes that co-benefit
4. A strong UX culture long term will provide better ROI of UI design efforts