18
User Requirements is a Fallacy VIJAY GEORGE 2016 OKLAHOMA CITY INNOTECH NOVEMBER 1, 2016 Copyright © 2016, Stratamation, All Rights Reserved
| Date post: | 12-Feb-2017 |
| Category: |
Technology |
| Upload: | joanna-cheshire |
| View: | 24 times |
| Download: | 2 times |
User Requirements
is a FallacyVIJAY GEORGE
2016 OKLAHOMA CITY INNOTECH
NOVEMBER 1, 2016
Copyright © 2016, Stratamation, All Rights Reserved
Do users know what they want?
Is it really a fair ask?
Copyright © 2016, Stratamation, All Rights Reserved
What are you really asking …
Copyright © 2016, Stratamation, All Rights Reserved
What you ended up with
Copyright © 2016, Stratamation, All Rights Reserved
Needed paradigm shift
Business Case and Governance
Requirements and Features
Development Cycle
User’s role in the system
IT’s role in the business
Copyright © 2016, Stratamation, All Rights Reserved
Business Case and Governance
Business case usually doesn’t say
make it work like it’s worked for the
last 20 years
We tend to assign project SMEs
from those knows the current
system really well
Without Leadership and
Governance they will steer toward
what they know
Importance of Organizational and
Human Change Management
Copyright © 2016, Stratamation, All Rights Reserved
Requirements and Features
Long feature list hardly used…
Feature List
Usa
ge
Long memory of what
happened in back in ’99
“I better get it now since it will
be another 10 years before
they listen to me again”
Proud of what they have created over the years
Copyright © 2016, Stratamation, All Rights Reserved
Development Cycle:
Building bridges and building software
Define Build Test Deploy
User’s role in the system
We tend to try to translate the physical
experience into the requirements for the system
User is not outside the system
Virtual changes the physical experience
Human Computer Interface has to be
experienced
User experiences of the system will be different
Leave room to learn through experience
Evolutionary nature of Change
Lessons from the startup world…
MVP
Experiencing it changes the requirements
Things change
Users learn
Development team learn
IT’s view of Business: Customer Service
Is that a good idea?
IT’s role in the business: Partnership
A better idea … IT is an integral part of the business
not separate that needs alignment
Most IT projects are business
transformation projects not just a
technology installation
Clear trade-offs help the business
make better choices
Trusted Partner vs. Service Provider
Why is everyone moving to Agile
Turn bigger projects into smaller cycles
Developers have to demo along the way
User’s experience changes the requirements
Recognizes the human part of the system
User and Developer part of the same team
Waterfall and Agile
Paradigm shift
Business Case and Governance
Leadership and Change Management
Requirements and Features
MVP and evolution through experience
Development Cycle
Iterative approach with teaming developers / users
User’s role
Recognize the human is an Integral part of the system
IT’s role in the Business
Partner and Trusted Advisor
Thank You
Contact Information:
Vijay George
Partner
Stratamation
360 Nueces Street, Suite-3010
Austin, Texas 78701
Phone: 512-297-8009
Copyright © 2016, Stratamation, All Rights Reserved
STR
ATA
MA
TION
