It’s a common mistake to think that Scrum is equal to Agile.

Being Agile is following the four principles of the Agile Manifesto. Scrum is a project management process consistent with those principles but it’s not, in and of itself, being Agile. XP (TDD, pair programming) is a development process, also consistent with those principles, and consistent with Scrum, but it is not being Agile. Continuous Integration, Continuous Delivery, DevOps, all consistent with the Agile principles.

Follow the principles, first and foremost. All of these buzz-phrases are just methodologies that people have found successfully help them to follow the principles. But the main part of “being Agile” is being able to adjust your processes at will where they don’t follow the principles of Agile.

Is Scrum agnostic to whether developers do agile practices?

Scrum is a set of guidelines that encourage a team to be agile.

Can you implement Scrum in a team that does not utilize automated
tests? does not perform refactoring or does not adhere to the agile
programming practices?

Very difficult, because by the end of every sprint you must have a working product. If you have to do a complete manual regression test to prove that it is working, this is likely to be unachievable.

Alistair Cockburn (one of the originators of the Agile movement) says this about Crystal Clear (one facet of his Agile methodology):

Crystal Clear can be described to a Level 3 listener in the following
words:

“Put 4-6 people in a room with workstations and whiteboards and access to the users. Have them deliver running, tested software to the
users every one or two months, and otherwise leave them alone.”

That is a definition of agile, admittedly for experienced development staff who know what they’re doing and can be trusted to get on and do it. So does that mean you have to use CI and TDD and Pair Programming and all the other fashionable things? Put simply… No.

Agile is not about following a set of processes, its about being effective. What that means to you depends on your team and how it works, what you find useful to you. If TDD doesn’t help you produce working code, then stop listening to the lesser lights who shout about it on the web and do not use it! If Pair Programming really helps your team to focus and get stuff done, then ignore anyone who says its a waste of time and organise your team like a 3-legged race at school sports day.

I did agile many years ago, so many we didn’t even realize we were doing agile – we delivered iterations of the product every month, and cycled round fixing bugs and adding new features regularly. We did absolutely zero unit tests as such things had not been invented, and the refactoring book had not been written. So yes, you absolutely can do agile without any of the so-called agile practices.

Alistair also says this of Kent Beck:

Asked about XP and the five levels of the Software Engineering
Institute’s “Capability Maturity Model,” he replied with XP’s three
levels of maturity:

1. Do everything as written.

2. After having done that, experiment with variations in the rules.

3. Eventually, don’t care if you are doing XP or not.

Eventually, don’t care if you’re doing XP or not… wise words that should remind you not to fall into this trap.

Scrum is a flavor of agile that follows a specific pattern to meet the goals of the agile development methodology. You can’t follow Scrum and not be agile, but you can be agile and not follow Scrum.

Scrum has no bearing on the use of automated tests, agile tends to favor them but the are by no means required. Refactoring should be a goal in agile and Scrum, but its often ignored. having no intention to ever refactor isn’t really agile.

Is agile about development or management?

Agile is a set of software development practices to meet flexibility and fast phase changing market requirements- or so called accelerated delivery. So in a big picture, it is about a flexible approach to meet the changing complex requirements of the client by splitting work in small peaces and delivering functionality in quick iterations of 2-4 weeks.

However to meet this flexibility, the development team needs to practice Agile programming practices.

Description from Wiki in regards to Agile software development:

Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.

Infact, you can use scrum in projects that have nothing to do with software development whatsoever. It’s a projectmanagement/team management method.

1) NO!!!! Scrum is Agile, meaning agile dev practices (TDD, pair programming, CI, refactoring, etc.) are very important to all aspects of a Scrum project. It is going to be much harder to figure out your teams run rate, estimate work, set appropriate sprint size, etc. if you are not using these practices.

2) Yeah you can implement Scrum in a team that does not adhere to agile practices, but I feel it really limits the potential of the team. A big part of why Scrum/Agile are so successful are the performance and quality gains you get from Agile dev practices which are core to delivering front to back complete features every sprint.

If someone else in your group is trying to convince you that Agile dev practices are a waste of time I think you should spend some time to emphasize why these practices are always stressed with Scrum as well as Agile as a whole. They really do make a difference.