Bookkeeping of requirements
In a recent Twitter discussion about requirements management, I wrote,
"Requirements management is like bookkeeping. You need to do it in business, but it doesn’t guarantee profits”
What is the purpose with requirements?
When talking about collecting requirements, one of the challanges is what we mean with requirements and level of detail. The requirements we ask for should also be possible to verify.
Is your design implementable?
One of the challenges with Enterprise Architecture and high-level design is that the solution looks good on paper, but is not possible to implement in reality. This is especially tough if we are trying some new types of solution, at least in this organisation.
Example of a high level design
Based on the need from the user and business model, a high-level design hypothesis looks like something like the image below. We have done some architecture work prior to sketching the design, i.e. an evaluation of different options of how the solution would look like, but that is a subject for a separate post.
The real cost of buying an IT-system
What is the real cost of buying an IT-system?
I would say, "Buying an IT-system is like buying a horse". It's often more expensive than you thought and you can see the video on youTube how to buy a horse