Cant we all just Scrum together?

Silicon Valley tv show sums it up well

Just starting out in the web development scene a lot of common terminology is lost on me. Terms like Scrum and Agile management would have gone over my head before this week. It’s a shame too because I have been searching for a way to stay goal oriented and focused for so long. Most people use Scrum in the workplace to break down an overall epic project and stay on track to meet deadlines and collaborate daily. I want to take a minute and break this down a bit further for those unfamiliar with the concepts.


This term Scrum was first implemented in 1986 when it referenced product development. Before this it was a rugby formation where the group of players stay close, keep their heads down and attempt to gain control of the ball. The point behind it was to increase speed and flexibility and was based on studies from a host of industries like the automotive, photocopier and lithography background. For scrum to be implemented you need to stay up to date daily. Since your looking at your goals so often with so many eyes the team can spot any deviations to the task at hand, and either implement changes or stay the course. Each member of the team is committed to reaching their goals so everyone can go hard during their sprints. There is no need to feel like your value is less then because it’s not just one person on the project and together can work through any challenges that may present themselves. While amid scrum no one works on anything other than the project presented to their team. This makes distractions irrelevant. This is where the Scrum master comes into play this person is a middle man between the teams and any outside influence. I have seen big boards divided into smaller segments with the goals labeled and notecards with smaller “chores” being transferred to other segments when completed.

Agile management comes into play with the use of scrum. Being able to readily adapt to any changes is the biggest take away for me with the twelve pillars of The Agile Manifesto, have a look for yourselves and let me know what you take away from it.

1. Customer satisfaction by early and continuous delivery of valuable software

2. Welcome changing requirements, even in late development

3. Working software is delivered frequently (weeks rather than months)

4. Close, daily cooperation between business people and developers

5. Projects are built around motivated individuals, who should be trusted

6. Face-to-face conversation is the best form of communication (co-location)

7. Working software is the principal measure of progress

8. Sustainable development, able to maintain a constant pace

9. Continuous attention to technical excellence and good design

10. Simplicity — the art of maximizing the amount of work not done — is essential

11. Best architectures, requirements, and designs emerge from self-organizing teams

12. Regularly, the team reflects on how to become more effective, and adjusts accordingly

Like what you read? Give Ant-DeGeorge a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.