So I’m about to head out there in the big bad world of UX design, and I’m reading what I can on the subject to learn the ins and outs of it all, what I can expect in a typical workday, office politics, and basically just how my life is gonna work once I’m in this industry.
I happened to come across this article: <a href=”http://www.sdtimes.com/blog/post/2011/11/11/Agile-slaves.aspx”>http://www.sdtimes.com/blog/post/2011/11/11/Agile-slaves.aspx</a>
I’ve heard a great deal of talk about Agile, its philosophy, how it works, et cetera. I like to think I have a good idea of its point and purpose. I was surprised to learn that it’s being done “wrong” – which is to say, the higher-ups at offices don’t seem to get the point, they’ve just latched onto the idea of being an “Agile shop” and are doing anything and everything they can that has the Agile name on it.
I’m aware enough of the outside world to know how often this kind of thing happens. It’s upsetting to see it happen with something as seemingly simple to understand as the Agile approach – start with a framework, then build your project in layers based on a hierarchy of importance of features. Just buying the Agile books and going to seminars isn’t going to make you an Agile shop. You have to actually get your project done to an acceptable level before it ships, and Agile is a straightforward way to do that, isn’t it? I supposed I’m just confused about how hard it actually is to BE an Agile shop once you’ve called yourself such.