Buzz words are thrown about at every company and we all roll our eyes at the mention of them. 'Scrum' and 'agile development' are not any different in the software world. While agile development can be very effective at helping a team launch a product, it also suffers from many built in flaws.
The most basic description of scrum can be summed up in one word, "meetings". And if you are just getting in to software development, beware of that simple little word. You will have daily "stand-up" meetings, bi-weekly sprint meetings, and meetings about how many f@!king meetings you are having! When you finally feel like you can sit down and write some code... BAM! Meeting! The daily meetings are usually 10-15 minutes, not bad, right? Wrong. Part of each team member's update is to ask questions and address any 'blockers'. If someone hit a wall with a task, this is where the clock just sloooows down. Then, the bi-weekly sprint meetings come along, which are usually about 4 hours...yes, FOUR HOURS! That is fours hours of meetings on a Friday afternoon, when all you can think about is, "Can I please just finish writing some code for once!" or "What can I have for dessert tonight?". Okay, maybe the second is just me, but you get the point.
Scrum is not just about meetings. You do get to play Poker! But no, not the fun kind of poker...it's called, "planning poker". In planning poker you sit down with your fellow team mates and your Scrum Master (yes, it's a real thing) and assign each task (I mean 'story') a Fibonacci number. The number is a point value that represents the difficulty and effort of said 'story'. Regardless of the end result, every Scrum Master will tell you (until they are blue in the face) that it does NOT represent time. As you complete more sprints, there will be a record of how many points you all can complete in that amount of time (again, usually 2 weeks). Then your Scrum Master will be able to better communicate with your 'product owner' about timelines (see, told ya it represents time).
In the end, you will have spent about 15%-25% of your work day talking rather than coding (your actual mileage may vary), arguing your point about why a story should be a 13 and not a 8, and the occasional words, "we are changing direction". Though, there is some good that comes from agile development. The team members have better accountability, increased organization, and the chance to voice your opinion about tasks and get help on 'blockers'. But, oh those glorious days when you could just put in your headphones, dim the lights, and code the day away!