@ -11,7 +11,7 @@ If you're not doing scrum, you're doing it wrong.
I've seen a lot of articles recently about how [Agile Does Not Equal Scrum](https://www.techwell.com/techwell-insights/2016/01/agile-does-not-equal-scrum-know-difference) or that you can [Determine the Right Agile Development Methodology](http://www.huffingtonpost.com/brian-de-haaff/how-to-determine-the-righ_b_9567344.html). Well, I can save you a bunch of time. The answer is that Scrum (or SCRUM if you're really in the know) is the answer. I think we can all agree that the [Agile Manifesto](http://www.agilemanifesto.org/) makes sense, what better way to follow that than Scrum!
For those not familiar with [Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)), let me start with a quick background.
For those not familiar with [Scrum](https://en.wikipedia.org/wiki/Scrum_%28software_development%29), let me start with a quick background.
You start with establishing a process for how code is worked on. You create a [Working Agreement](http://www.slideshare.net/paytonconsulting/agile-team-working-agreements) to make sure that no one is special or has their own way to do things. Importantly, on top of that you need to make sure all the tools you are going to use are defined and enforced up front. For example, if you are working on a Java project make sure you rely on IntelliJ's `.idea` files as the only way to build and deploy the project. Even if someone is wildly more efficient with Eclipse, they need to be part of the team.
Adam Weiss
