Design for additional requirements, or not?
Do you need architecture when doing agile development? The philosophy of Agile is to do the least amount of something and no more for a given situation, but is this always a good approach?
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.
Legacy software that provides value
Woody Zuill and Greger Wikstrands talks about the value we get from from legacy software, but also the need to continuously improve the code base.
How to define a service
How to define a service in a good way is like asking for how long a string is. It depends is the usual answer.
Two common problems for designers and developers as of today
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.