“Requirements simply don’t exist…

“Requirements simply don’t exist. A requirement, by definition, is something required: the basis for a contract, a way of managing an external service provider, part of a deal where a buyer promises money and a contractor promises to deliver something well-defined. But within an enterprise, what does it mean for something to be “required”? A requirement purports to express a necessity, but where could this necessity come from? In a publicly held company, maximizing shareholder value might be a necessity, but how could a particular feature of an application be necessary when there might be many other ways of maximizing shareholder value?”

Mark Schwartz – A Seat at the Table: IT Leadership in the Age of Agility

Header Image: A spring sunrise taken on one of my pre-work walks. This was one of those cold and crisp days when sunrise often seems so vibrant.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.