Skip to main content
Post Made Community Wiki by Dunk
Fixed typo
Source Link
user2567
user2567

I was a big fan of UML a while ago. I'm even OMLOMG certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner (or analysts) AND his (their) dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

I was a big fan of UML a while ago. I'm even OML certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner (or analysts) AND his (their) dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

I was a big fan of UML a while ago. I'm even OMG certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner (or analysts) AND his (their) dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

added 22 characters in body
Source Link
user2567
user2567

I was a big fan of UML a while ago. I'm even OML certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner (or analysts) AND his (their) dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

I was a big fan of UML a while ago. I'm even OML certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner AND his dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

I was a big fan of UML a while ago. I'm even OML certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner (or analysts) AND his (their) dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

rework
Source Link
user2567
user2567

I was a big fan of UML a while ago. I'm even OML certified and. I used it extensively in one of biglarge enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner AND his dedication to the development team to give more details as needed.

UML is a tool you can use or not, but it's certainly not a critical factor for the success of your projects. TheAfter many years, I now think the critical factor is the development team, not itsno matter which tools it uses.

I was a big fan of UML a while ago. I'm OML certified and used it extensively in one of big projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems.

I now prefer working with user stories, supported by both necessary documentation written by product owner AND his dedication to the development team to give more details as needed.

UML is a tool you can use or not, but it's certainly not a critical factor for the success of your projects. The critical factor is the development team, not its tools.

I was a big fan of UML a while ago. I'm even OML certified. I used it extensively in large enterprise projects I was involved in.

Today, I stopped UML almost completely. Sometimes, I use the sequence diagram that I find very useful to describe interactions between systems, but no other diagrams.

I now prefer working with user stories, supported by both (only) necessary documentation written by product owner AND his dedication to the development team to give more details as needed.

UML is a tool you can use, but it's certainly not a critical factor for the success of your projects. After many years, I now think the critical factor is the development team, no matter which tools it uses.

Source Link
user2567
user2567
Loading