I heard about Scrum in college and it sounded great. I said to myself: if I ever work in a team, I want to put Scrum into practice. And so we did… partly.
Scrum is an agile software development framework. Agile means that the team knows that conditions can rapidly change in software development and that one just can’t plan for the future like it’s done in „traditional“ project management. In short, agile software development advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change.
The Scrum team works self-organized and its members are in close contact with each other. The team works as a single unit to reach common goals. Practice shows that communication is the key for addressing changes as fast as possible. There are daily meetings (called ‚Daily Scrums‚) and plenty more meetings within a Sprint.
I wanna emphasize that in our current situation, we simply couldn’t implement Scrum in it’s pure form. We needed to loosen the restriction that the Product Owner and the Scrum Master are not allowed to assume the role of a „normal“ developer. We don’t have the ressources to go without imporant skills needed for the actual development process. I also need to say that we by ourselves are still in the learning process. But I thought it may be interesting for other teams to see how it can/should/shouldn’t (decide by yourself) be done. I read a wonderful book about Scrum but it would have been great to also get some ideas of how to implement it in real life. So in the following section I’ll tell you how we try to use Scrum as an agile project management principle and how we adapted the process to fit our needs.
Leave a Reply
Want to join the discussion?Feel free to contribute!