The Agile Manifesto and its accompanying principles describe in abstract terms how developers and teams should build software. By design it contains no concrete details. For example, one of the principles is:
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
How do you make sure that developers communicate face-to-face?
Business people and developers must work together daily throughout the project.
How should they work together? What does that mean?
Scrum is an implementation of Agile. It is a set of guidelines that, if followed, should mean that a team is working according to Agile principles. Whether or not that is the case is debated. Some would say that you can practice Scrum but totally lose sight of Agile. That doesn't make Scrum bad. It just means that we have to understand the underlying principles.
Here's some interesting reading on how the success of Scrum depends on Agile principles:
The Agile Manifesto and its accompanying principles describe in abstract terms how developers and teams should build software. By design it contains no concrete details. For example, one of the principles is:
How do you make sure that developers communicate face-to-face?
How should they work together? What does that mean?
Scrum is an implementation of Agile. It is a set of guidelines that, if followed, should mean that a team is working according to Agile principles. Whether or not that is the case is debated. Some would say that you can practice Scrum but totally lose sight of Agile. That doesn't make Scrum bad. It just means that we have to understand the underlying principles.
Here's some interesting reading on how the success of Scrum depends on Agile principles:
The True Corruption of Agile
FlaccidScrum - that's really the title. There's no space in it.