Scrum is commonly known by many project managers and especially when looking at software projects you’ll find that a lot of them are using some kind of Scrum. Scrum is a framework for project management that can be applied to all types of projects. Scrum is an iterative process which builds the product in small steps called Sprints. Scrum excels in keeping a high level of communication with the customer and making sure that the promised deliverables is going as planned. Working agile and being open about the process and letting the customer decide what is important creates a good environment for the team and the customers are happy because they get what they want and when they want it = high quality work!
I have to admit that i love the way Scrum works and how it benefits a software process. In my final project where I’m developing a stock exchange game for young students, I’ll be using Scrum to manage my project. I chose Scrum because I want to get the same benefits as a full Scrum team does. To reach that goal I’ll probably have to make some changes along the road to avoid overhead activities. I intend to share my findings on this blog, and share pros/cons of this method. I’ll start with all activities and see how things goes to determine what I can benefit from, and which activities to exclude.
So remember to check in soon to follow my progress on “Scrum for the one man team”.