SCRUM is an important strategy used for software development. However, developers may face specific issues considered relevant that might fail to lead to the best solutions implemented or result in longer development times. Literature has a significant number of ”best practices” to guide development teams; however, sometimes are very theoretical and may or may not be relevant to a particular environment or organization. This study evaluated these best practices in terms of if they were properly followed and how effective they were within various organizations. Aiming to gather information as to how tasks are actually performed as compared to SCRUM standard practices, the study performed a survey to software developers, product owners, and others. The survey focused on gathering and presenting data on the perceptions, needs, activities and issues from the various Scrum traditional roles involved in software development. A questionnaire was designed that included 15 multiple-choice questions and 2 open ended questions, Questions related to effectiveness of collecting development features/requirements, daily meetings duration, overall efficiency of the Scrum structure, and interactions with Product Owners all were distributed within multiple organizations. Overall, the study compared the implementation and use of SCRUM effectiveness based on traditional methodology SCRUM methodology. The study was designed to aid all roles involved in scrum when implementing such a framework within an organization. This study focused on specific features considered relevant for successfully developing systems using SCRUM as methodology. Among these features, the focus were on: (1) is the ticket allocation strategy effectiveness for the development processes? (2) are the daily stand-up meetings efficient and do they represent an important activity during the process? (3) is the timeline defined for each sprint appropriate? and (4) are the team members improving their capabilities on designing, coding and testing activities as they might be allocated to perform a variety of front or back-end development activities? As with other best practices, whether software development related or in other industries, theoretical guidelines should only serve as a basis for implementation as each organization has its unique characteristics, varying number of software developers, and local requirements.

SCRUM是用于软件开发的重要策略。但是，开发人员可能会面临被认为相关的特定问题，这些问题可能无法导致实施最佳解决方案或导致更长的开发时间。文献具有大量的“最佳实践”来指导开发团队。但是，有时这是非常理论性的，可能与特定环境或组织无关。这项研究从以下方面评估了这些最佳做法：是否正确遵循了这些最佳做法以及它们在各个组织中的有效性。为了收集与SCRUM标准实践相比如何实际执行任务的信息，该研究对软件开发人员，产品所有者和其他人员进行了调查。该调查的重点是收集和呈现有关感知，需求，来自软件开发中各种Scrum传统角色的活动和问题。设计了一个问卷调查表，其中包括15个多项选择题和2个开放式问题，与收集开发功能/需求的有效性，日常会议持续时间，Scrum结构的整体效率以及与产品负责人的互动有关的问题都分布在多个组织中。总体而言，该研究比较了基于传统方法SCRUM方法的SCRUM有效性的实施和使用。该研究旨在帮助在组织内实施这种框架时参与scrum的所有角色。这项研究集中于被认为与使用SCRUM作为方法成功开发系统相关的特定功能。在这些功能中，重点在于：（1）票务分配策略对开发过程是否有效？（2）日常站立会议是否有效，并且在此过程中是否代表重要活动？（3）为每个冲刺定义的时间表是否合适？（4）团队成员是否提高了他们在设计，编码和测试活动中的能力，因为他们可能被分配执行各种前端或后端开发活动？与其他最佳实践一样，无论是与软件开发有关的行业还是其他行业，理论准则都应仅作为实施的基础，因为每个组织都有其独特的特征，数量不同的软件开发人员和本地要求。