Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
What is the difference between Agile and Scrum? When software development teams are formed under the purview of a corporate management service or a software provider, a selection process is used to determine which project management method best suits the teams. In essence, these selection procedures are formalized in what is called Scrum or Agile selection methods.

SAP Agile and Scrum What is the Difference








These two methods of software development differ because Agile is self-directed and self-organized. In contrast, Scrum is formally motivated by a stakeholder's need for a product or deliverable within a defined time period. Many companies use Agile as the first step towards project delivery, while others choose to begin with Scrum and customize it based on their own internal needs. In essence, Agile is a methodology of working that is driven primarily by business owners and developers. Its formalized structure enables regular and timely feedback from project managers. On the other hand, Scrum is self-driven by project managers whose responsibility is to manage the process during each phase. This may include obtaining technical support from external resources, solicit opinions and suggestions from team members and perform post-project retrospectives.


The difference between Agile and Scrum can be illustrated by looking at the team selection process for Agile. A team selection procedure may look something like this: Team A develops a module, Team B completes it, and Team C improves it. In Agile, the process is formalized by requiring each team member to present a written description of their development experience and a description of the tasks they will complete. The team reviewed the description, and if it is deemed appropriate, the team assigns the job to a tester or an architect. If the description is not acceptable, then the job goes to the team manager, who reviews the entire process and makes the final decisions.


As mentioned above, both Agile and Scrum follow a formalized process. But there are key differences between the two methods. In Agile, users are usually part of the process. They provide feedback, suggest modifications and improvements, and vote on issues. With Scrum, you have the same type of participation, but more of a management structure followed.


For Scrum, the focus is less on involvement by the customer. Testers provide a level of testing for functionality, performance, user interface design, and testing code. There is little if any involvement by the Product Owner or the Software Development Team. When teams are formed to address the project, they must meet in a room with the Product Owner to discuss the scope and work objectives for the project.


One of the benefits of using Agile development is the possibility to reuse much of the original code. This can be especially true for large or complex projects that take a long time to complete. In a formalized process, changes are required frequently and often need to be redone. In Agile, most changes can be implemented in a single patch. The end result is that there is a much smaller chance that an issue will lead to a need to rewrite the entire project.


Another difference between the two methods is the length of a project. With a formalized process, a new project begins immediately. On the other hand, Agile methodologies allow a project to grow in the "iterative" method. This is done by providing a series of requirements, narrowing them as the project progresses until a point at which the team members are comfortable with the current definition. The longer the iterative process, the more likely acceptance will occur sooner than in a formalized process.


Agile is generally more flexible because it doesn't require you to create task lists and set up milestones. Because of this, you can adopt a "lightweight" approach, where you add task lists as the project progresses. You might do this for each task and then distribute them throughout the team. Because Agile is largely a collaborative effort, team members will be very excited when assigned tasks. If you implement Agile in your company, you'll find that it tends to bring your team members together, working as a unit to solve the problem at hand.
Labels in this area