To many requirements
Are your requirements gathering like a making a wishlist for Christmas?
In this episode Casimir Artmann talks about when you have to many requirements and the consequences for business.
Posted in: Enterprise architecture
Are your requirements gathering like a making a wishlist for Christmas?
In this episode Casimir Artmann talks about when you have to many requirements and the consequences for business.
How to define a service in a good way is like asking for how long a string is. It depends is the usual answer.
Designers and developers have two common problems today.
The business requirements are not yet ready, in order to be able to deliver a solution in time to the business.
For a few weeks, I've been blogging and talking about Service Management and ITIL in an more agile world.
I'm very doubtful if a traditional EA approach would work for a technology oriented startup if we look at their time line and how the market for where they want to sell their products evolves.