From The Principles of Agile Modeling (AM):
Every artifact that you create, and then decide to keep, will need to be maintained over time. If you decide to keep seven models, then whenever a change occurs (a new/updated requirement, a new approach is taken by your team, a new technology is adopted, …) you will need to consider the impact of that change on all seven models and then act accordingly. If you decide to keep only three models then you clearly have less work to perform to support the same change, making you more agile because you are traveling lighter. Similarly, the more complex/detailed your models are, the more likely it is that any given change will be harder to accomplish (the individual model is “heavier” and is therefore more of a burden to maintain). Every time you decide to keep a model you trade-off agility for the convenience of having that information available to your team in an abstract manner (hence potentially enhancing communication within your team as well as with stakeholders). Never underestimate the seriousness of this trade-off. Someone trekking across the desert will benefit from a map, a hat, good boots, and a canteen of water they likely won’t make it if they burden themselves with hundreds of gallons of water, a pack full of every piece of survival gear imaginable, and a collection of books about the desert. Similarly, a development team that decides to develop and maintain a detailed requirements document, a detailed collection of analysis models, a detailed collection of architectural models, and a detailed collection of design models will quickly discover they are spending the majority of their time updating documents instead of writing source code.
I tend to apply that Agile Modelling principle to pretty much everything in life. Travel light.
Including TW’s features. If I can do everything I need with a small subset of the features, then I only use that subset that facilitates no sticks in my cognitive wheels and no cognitive wheels in the mud.
When I need to solve a problem that can only be solved by a feature I’ve never needed, then I add that feature to my “go to” toolkit.
BTW:
Some folk see this is a negative for some reason. If you dogmatically insist on using every feature provided to handle every single thing intended to be handled by every specific feature, cool. Whatever floats your boat. Respect, but I don’t care. It is your boat, and you should do everything needed to keep your boat afloat. I have no intention of sinking your boat.
If whatever floats your boat is something that sinks mine, why would you be bothered by me doing whatever is needed to keep my boat afloat?