The term "content management system" means different things to different people. Sometimes, when discussing CMS, I'll realize that the term "web" is omitted from the conversation but absolutely implied. A web CMS is quite different than a CMS like RSuite. So when selecting a CMS, getting ready for a CMS project, or implementing a CMS it's important to establish your definition and communicate that to your team.
Teams struggle because there is not always a shared vision of what they are undertaking and, depending on perspective, team members have a different focus in mind. Some folks focus on the need to store all content in a common repository, others think about workflow management, and still others may be fixated on content structure and delivery.
With these things in mind, I define a content management system as the processes, technologies, and people involved in acquiring, preparing, and delivering content. This definition ensures that all aspects of content management are considered and ultimately leads to a better understanding of necessary technology components. You may find that there are process changes or organizational changes that are equally important as implementing technology.
Technology is an enabling device. Technology won't manage your content any more than a filing system will file your documents. Be prepared to think hard about the processes that make up your content management system and how people interact with the content and that process. There's no point implementing a Content Management System if you don't intend to manage your content!