It isn't all about the code?
This is the coneblog journal and related categorized archives. You can read the blog as written back to front, or browse the categorized archives at right - check out the about categories for guidance on that is where. For a quick overview of the types of content you might run into, check out the Best of coneblog - some of my personal favorites.
Letter to a PM – Going to the Customer
I’ve been reflecting about your questions in our talk yesterday. Here is my understanding of your concerns:
A Brief History of Change – The Future of Change
We have looked at Change as a barrier and an opportunity. What can we say about the future of Change Management in software development?
A Brief History of Change – System as Change Driver
Another change concept is the system as change driver. In this model, the requirements of the system represent the “right” business model, and the challenge is to change the user culture, processes and workflows to match the better model, as captured in the system.
A Brief History of Change –If a Need is Voiced by A User…
And no systems analyst is there to hear it and document it, does it represent a valid requirement? Like trees falling in the forest, this might seem like a frivolous question, but it gets at some important Requirements issues.
A Brief History of Change – Requirements Quantum Effects
Today even Change has changed. Indeed we know today that everything changes constantly: the users needs change, the business drivers change, the company gets bought or sold, the delivery platforms change, the interface environment changes, the industry standards change, and the development processes change.