Scrum

Before I started working, I had never heard of this approach for working. I had heard of Agile, and I had read a lot about DSDM. But Scrum for me was a new word. So when I got to know that now my work would be dictated by this approach, I went home and did my homework. I researched it, read some material, and tried to understand what it really is. And I liked what I found.
A fact that people that push Scrum like repeating a lot is that it is not a methodology. (They also like to say that it is not a cure-all/panacea/silver bullet). Scrum is a form of Agile. In Scrum everything is time boxed. You are given a finite and unmovable amount of time, and you say what you will achieve in that time. You have the product back log, from where you choose what work to do. This is chosen based on business value, which means how much it will help the company. Then you have your iteration ( which in our case is normally two weeks), during which every day you say what you have done from the last meeting, what you plan on doing till the next meeting, and any impediments that might be keeping you back. The team can also have some tool to help them keep in touch on who is doing what.
Before the iteration the user stories are estimated, and at the end there is the review, and retrospective. An important factor is that the team is self managed. Two important roles in Scrum are the product owner, and Scrum Master. I will not explain what they do, because all over the Web there are definitions. I don't have a lot of experience as to what to compare Scrum, but I can say that in my case I have found it to work very well, and I like the way work is done efficiently and responsibly under it.