For a properly-configured Maven project, once Maven is installed, you should be able to run the build and it should work. But I can think of two things that might go wrong (other than networking issues):
1) The project relies on a repository other than the default one, in which case you must declare the alternate repository in your m2_home/conf/settings.xml file
2) The project relies on artifacts that were manually loaded in a local repository by the person who put together the pom.xml. In such a case, the provider of the project should provide documentation on which artifacts must be manually installed.
If this does not help you, then I will state that you can usually get better responses to questions if you state up front what error you are seeing.
For your own project, the Maven install is all you need. Be aware that the first time couple of times that you run Maven it will take extra time because it will have to download various JAR files from the remote repository. But after those first few times, the builds should go much faster, at least until you try something different or want to access other libraries, in which case more JARs will be downloaded.
You might want to get "Better Builds With Maven", or "Maven The Definitive Guide", both free downloads and helpful to get you started.
"mvn install" doesn't mean what you think it does. It means "build the artifact and install it into the Maven Repository.
If you want to make an OS-installable application, you need to set up your own installation process. That means figuring out what directories you want the installed app to live in, setting up its config files (if any), creating and copying the scripts needed to run it (if any) and so forth.
For the most part, you'll be on your own. But for Red Hat/Fedora systems there's a Maven plug-in that can create RPM install packages and it works very nicely. You will need a good understanding of how RPMS are constructed, however.
Customer surveys are for companies who didn't pay proper attention to begin with.