Something about requirements which change everything

Nowadays the software development lifecycle never stops. Customers generate new needs, analysts gather new requirements and developers implement it. In such situations, the probability that every new requirement will change an architecture increases dramatically. 

We will discuss why some requirements can be implemented with two strings of code only while others lead to "Seems we should buy another 3 DB Servers"? Why some change requests are "that's OK", but others like "We'll all die!!!". Will try to understand together and discuss how to avoid it.

Audience level
Regular Talk (40 min)

Comments

{{comment.AuthorInfo}}
{{ comment.DateCreated | date: 'dd.MM.yyyy' }}
Your review is now here. Continue to communicate with the speaker
Chat with us, we are online!