The process by which most enterprise software is developed is fatally flawed. There are flaws in any software development process, but in the past 13 years I’ve seen one approach produce more bad software and blow more budgets than any other: requirements-driven software development. Thankfully, I’ve also had the opportunity to see the success of an alternative type of process, a process in which user experience design drives what gets developed. This type of process helps teams deliver good software on time and within their budgets.
Archive for the ‘Business Analyst’ Category
Requirements-Driven Software Development Must Die
Monday, July 25th, 2011Where business analysis and user experience intersect: the benefits of collaboration
Monday, July 12th, 2010According to Harvard Business Review editor Julia Kirby, 2010 may be the year for a resurgence in companies reconnecting with their users and focusing on user experience, but don’t forget about business analysis! It’s the BA’s job to ensure that the issues and business objectives are understood. When the solution involves end users (of a new or enhanced application/website/product), that’s where we need team up with a user experience (UX) professional.
