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?
Posted in: Enterprise architecture
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?
When reviewing programs, projects and solution designs from an architecture perspective, I often see people doing the same mistakes as others have done before. I did some of them 25-30 years ago and I see people doing the same mistakes today.
IT is not fashion, so why do I need a new IT-platform?
When a client want a new IT-platform, my question is why? Isn’t the old one still usable? If they have a hard time to give a reasonable answer, I try to ask some leading questions.
A few days ago, at the local harbour, we chatted a little bit to a guy that was a project manager. He told a recent story that made me think about how we work in the IT industry today.
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.