Email
Favorite
Favorited ×
Download
Embed
Private Content
Copy and paste this code into your blog or website Copy Customize Close
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

+ Follow

UX in ZOOM

by ZOOMInt on May 31, 2011

847 views

Early experience with bringing usability to ZOOM International. What I did in the first eight months and how that worked. Slides for my UX Camp CZ speech.

More…

Early experience with bringing usability to ZOOM International. What I did in the first eight months and how that worked. Slides for my UX Camp CZ speech.

Less

3 Embeds 594

http://www.zoomint.com	592
http://translate.googleusercontent.com	1
http://webcache.googleusercontent.com	1

Statistics

Favorites: 1
Downloads: 0
Comments: 0
Embed Views: 594
Views on SlideShare: 253
Total Views: 847

- I do not share knowledge, do not have blog\n\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- might sound boring, but it is not\n- one flagship product, another merging into it and new emerging product\n
- we will skip childhood, school, university\n
- we will skip childhood, school, university\n
- we will skip childhood, school, university\n
- we will skip childhood, school, university\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- I actually found just 9 differences\n
- lorem ipsum story\n
- lorem ipsum story\n
- lorem ipsum story\n
- lorem ipsum story\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
- not only developers\n
\n
\n
\n
\n
- somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
- somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
\n
\n
\n
\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- 50 projects (epic - 2 or more sprints)\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
- it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- developers are also fundamental\n- http://www.zoomint.com/en/jobs/129-senior-software-engineer\n- 5 years experience, persistence frameworks, english, GWT\n
\n
\n

1 Favorite

sachinbhavsar 12 months ago

UX in ZOOM — Presentation Transcript

UX in ZOOM Vaclav Slovacek vaclav.slovacek@zoomint.com
ZOOM
ZOOM• call recording, agent evaluation, speech analysis
ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit
ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries
ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers
ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers• your voice is heard
ZOOM• call recording, agent evaluation, speech analysis• Google Web Toolkit• about 500 customers in 50 countries• about 10 developers• your voice is heard• ﬂexible and evolving
UX Designer
UX Designer• at ZOOM for 8 months
UX Designer• at ZOOM for 8 months• in product management
UX Designer• at ZOOM for 8 months• in product management• writing speciﬁcations
UX Designer• at ZOOM for 8 months• in product management• writing speciﬁcations• long term design decisions
UX Designer• at ZOOM for 8 months• in product management• writing speciﬁcations• long term design decisions• planning and prioritization
UX Designer• at ZOOM for 8 months• in product management• writing speciﬁcations• long term design decisions• planning and prioritization• day-to-day consulting
My Story no!ing more
Preparation
Preparation
Preparationseeing ZOOMs product
Preparationseeing ZOOMs product studying stuff about user research
Preparationseeing ZOOMs product studying stuff about user research user research cost calculator
Preparationseeing ZOOMs product studying stuff about user research user research cost calculator playing with prototyping tools
First Days
First Days
First Daysdesigning a new player
First Daysdesigning Excel report template designing a new player
First Daysdesigning Excel report template checking implementation designing a new player
First Daysdesigning Excel report template checking implementation designing a new player discussing what went wrong
10 differences game
10 differences game
10 differences game
10 differences game It is totally different from the prototype.
10 differences game What is the difference?
10 differences game What is the difference?explain why features are important
Unusable Speciﬁcation
Unusable Speciﬁcation
Unusable Speciﬁcation
Unusable Speciﬁcation usability of speciﬁcations matters
Quick Fixes
Quick Fixes
Quick Fixesredesigning toolbars
Quick Fixesﬁxing a customers issue redesigning toolbars
Quick Fixes developers coming to askﬁxing a customers issue redesigning toolbars
Request Origins
Request Origins
Request Origins
Easier Development /browse/SC-2150 and we had a lot an had s olved http://jira:81 EC” speciﬁcation.Ju problems with foll owing “As in CallRof logical t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu
Easier Development /browse/SC-2150 and we had a lot an had s olved http://jira:81 EC” speciﬁcation.Ju problems with foll owing “As in CallRof logical t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu
Easier Development /browse/SC-2150 and we had a lot an had s olved http://jira:81 EC” speciﬁcation.Ju problems with foll owing “As in CallRof logical t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu ask why a feature is requested
Triangle
Triangle
Trianglesimple
Triangle simpleeasy to develop
Triangle simpleeasy to develop ﬂexible
Triangle simpleeasy to develop ﬂexible
Triangle simpleeasy to develop ﬂexible
Projects Boom
Projects Boom
Projects Boomlong term projects speciﬁcations
Projects Boom UX Guidelines and checklistlong term projects speciﬁcations
Projects Boom 2011 vision presentation UX Guidelines and checklistlong term projects speciﬁcations
Projects Boom 2011 vision presentation talk with users UX Guidelines and checklistlong term projects speciﬁcations
Projects Boom 2011 vision presentation talk with users vision for developers UX Guidelines and checklistlong term projects speciﬁcations
Projects Boom tuning speciﬁcations 2011 vision presentation talk with users vision for developers UX Guidelines and checklistlong term projects speciﬁcations
Speciﬁcation
Speciﬁcation
Speciﬁcation
Speciﬁcation
Speciﬁcationmedia are stronger than text
Project
Project 1 Project 2
Project 1 Project 2
temporary featuresProject 1 Project 2
critical stuff ﬁxed now vision of the futureProject 1 Project 2
InspirationMan, I feel excited about every new feature we design now. I feel totally inspired.
InspirationMan, I feel excited about every new feature we design now. I feel totally inspired. do not design alone
Agile
Agile
one week planning of 4 sprints Agile
one week planning of 4 sprints Agile daily meetings
one week planning of 4 sprints Agile daily meetings review
one week planning of 4 sprints Agile daily meetings review retrospective
one week planning of 4 sprints next sprint Agile daily meetings review retrospective
Agileone week planning of 4 sprints daily meetingsreview retrospective next sprint
Agileone week planning of 4 sprints 15 enhancements having 200 tasks daily meetingsreview retrospective next sprint
Agileone week planning of 4 sprints 15 enhancements having 200 tasks more accurate estimates daily meetingsreview retrospective next sprint
Agileone week planning of 4 sprints daily meetings know what is happeningreview retrospective next sprint
Agileone week planning of 4 sprints daily meetings know what is happening enforce relationship with developersreview retrospective next sprint
Agileone week planning of 4 sprints daily meetings different kind of feedbackreview retrospective next sprint
Agileone week planning of 4 sprints daily meetings different kind of feedbackreview notes for next sprint retrospective next sprint
Agileone week planning of 4 sprints daily meetingsreview improving communication retrospective next sprint
Agileone week planning of 4 sprints daily meetingsreview improving communication retrospective know what you do wrong next sprint
Future
Future
FutureUser Research 2011
UX Checklist use during testing FutureUser Research 2011
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical s
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical s 20 ca ll c en te rs
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 ca up ll c s en te rs
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 ca up 3 re ll c s en te sear rs che rs
UX Checklist use during testing FutureUser Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 half a y ca up 3 re ll c s en te sear ear rs che rs
UX is fund
UX is fundamental for your company
recommendations
explore
explore
seek inspiration
we are lookingfor developers
Q&Avaclav.slovacek@zoomint.com
Thank you for your attention

UX in ZOOM

by ZOOMInt on May 31, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 594

Statistics

UX in ZOOM — Presentation Transcript