Today’s business world is no longer what it was 20 years ago; competition forces us to meet perfectly customer needs by delivering value and quality, which is almost impossible without using effective project management. It helps to ensure that projects reach the necessary quality by balancing the budget, time constraints, and scope. Software development projects, like any other domain, have become increasingly competitive and value-based, which has pushed many organizations to adopt “agile” cultures and methodologies as a management style to build their products to respond more quickly to change while taking into consideration the business need. These agile methods and the acceleration of their adoption have established and reinforced the mindset of change, but it wasn’t enough to guarantee the delivery of software development products that correspond to customer needs. There are several agile methods, each one can be adapted to a different context; the most used is Scrum. In this article we will explore the Scrum method using an example of project organization in order to identify its limits. These limits can be the reason for not perfectly responding to a customer need and therefore not succeeding in satisfying it. These reflections were addressed in this article in order to improve collaboration in software development projects.