15
ake Software for Users, ot Stakeholders Rostyslav Belmeha Front-End Developer @SoftServe

Make software for users, not stakeholders

  • Upload
    -

  • View
    104

  • Download
    1

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Make software for users, not stakeholders

Make Software for Users,not Stakeholders

Rostyslav BelmehaFront-End Developer @SoftServe

Page 2: Make software for users, not stakeholders

1. Converting Ideas into Apps2. Design

a) Requirements Specificationb) Solution

AGENDA

Page 3: Make software for users, not stakeholders

Converting Ideas into Apps

Page 4: Make software for users, not stakeholders

Converting Ideas into Apps

Requirements

Design

Implementation

Verification

Maintenance

Page 5: Make software for users, not stakeholders

DesignRequirements Specification

Page 6: Make software for users, not stakeholders

Design. Requirements Specification

Process:

• business analysts and designers create a clear picture of the product• decisions are based on previous experience, stereotypes of users'

needs, personal preferences• the emphasis is on graphic design element, rather than interaction

and usability

Page 7: Make software for users, not stakeholders

Problems:

• random stereotypes about the user;• personal preferences;• wishes of the end users who do not know about the rest of the opportunities

that new software will offer;• decision belongs to someone whose status is higher.

Design. Requirements Specification

Page 8: Make software for users, not stakeholders

Aspects, which are left out of focus:

• The goals of the user;• Convenience and efficiency;• Intuitiveness and ease of use.

Design. Requirements Specification

Page 9: Make software for users, not stakeholders

DesignSolution

Page 10: Make software for users, not stakeholders

Design. Solution

Creating personas

• sex• age• education• family situation• level of computer education• etc

Page 11: Make software for users, not stakeholders

Design. Solution

Choosing the key persona

• personal experience of the UX specialist• communicate with potential users

Page 12: Make software for users, not stakeholders

Design. Solution

Test prototype with real users

• UX specialist define a set of specific tasks• test sessions a few times• representing the result in numbers

Page 13: Make software for users, not stakeholders

Methods which should be applied:

• Understanding portrait of typical users• Creating personas and defining tasks for each workflow• Iterative approach to interface design• End user testing

Design. Solution

Page 14: Make software for users, not stakeholders

Conclusion

Page 15: Make software for users, not stakeholders

Questions?