Another goal that we want to achieve during data modeling is extensibility. That is, the data models we build should be able to be extended to accommodate new requirements with minimal impact on the existing data structure, and the effort required to make those changes should be small. Being extensible doesn't mean that the data models should be able to adapt to all kinds of changes, which is impossible and usually leads to the model becoming over-designed. The extensibility that we should achieve is based on a deep understanding of the application requirements, and also through discussions with business specialists to foresee possible requirements in the near future. For example, in the TaskAgile application, we don't have the requirement to create organizations above teams or provide the ability to invite people to join a team (in the current user stories, we only allow adding people to boards). These are examples of features that we might need to implement in the next version. And, when we design the data models, we definitely need to keep these in mind and make sure we have extensibility in our data models.