SCRUM, What is it? How did we do?
What is the process?
Scrum is the iterative process of software or developing projects.A backlog of all the items that need to be developed is created at first (although it can always be changed).
After that the sprint planning comes after and can be up to a month but usually a shorter period.
Within the sprint planning you need to make sure you know what will be done and by who, also if there is some risk to the item(s) and a Quality Assurance should be appointed aswell.
From there you have a sprint backlog.
thereafter the iterative process begins and everything gets implemented by each team-member.
And after that a possible shippable/sellable product has been made.
After that there will usually be a sprint retrospective and a sprint review to understand what needs to be refined and or done next.
How has it gone for my team using Scrum?
In my opinion scrum has been perfect for our development. While we might not always have a clear picture of what the final design will be, many ideas have come forth and possibly have made the game better in certain ways, for example we had a problem deciding on how the background of our game would act, and we went through two iterations to perfect it, and had we had a pre planned idea it would likely not have been as good as we wanted it to be.
The sprint planning might be quite long sometimes, because we might go back a lot to put items in our product backlog and then create a new plan based on that.
We might have been kind of lazy when it comes to daily stand ups, at least on my part, and I can admit that. But it should be done to be able to understand what others might have a problem with and what their progress is with their items.
And when the sprint review comes it is great to know how many percent of the items were done so that we might limit or increase the amount that we can do each week. In our case we wanted to avoid having less than 50% of all the items done,
The sprint planning might be quite long sometimes, because we might go back a lot to put items in our product backlog and then create a new plan based on that.
We might have been kind of lazy when it comes to daily stand ups, at least on my part, and I can admit that. But it should be done to be able to understand what others might have a problem with and what their progress is with their items.
And when the sprint review comes it is great to know how many percent of the items were done so that we might limit or increase the amount that we can do each week. In our case we wanted to avoid having less than 50% of all the items done,
What can be improved?
The product backlog is not something we have looked over as much as our planning, which might make us lose sight of what will need to be done sometime.
Daily stand ups as I mentioned before needs to be done correctly( Even by me! )
Meetings should be less arguing and less disagreements, and letting someone take charge of certain decisions that need to be made.
Daily stand ups as I mentioned before needs to be done correctly( Even by me! )
Meetings should be less arguing and less disagreements, and letting someone take charge of certain decisions that need to be made.
The way you divided your text and put the different parts of it under headlines made the post easy to follow and to what was what.
ReplyDeleteI feel like your introduction on how the process is done started of really good, but towards the end of it you jumped a bit back and forth. In the second to last sentence you write about a finished product, but in the following sentence you start of with “after that” and describe something that probably should’ve been introduced earlier.
In the second part you do a good job in describing how your experience of scrum have been. It’s interesting to read what you felt were the positives and what setbacks you’ve had. Something that I would like to have been included is some more depth on the stand up meetings. Have you felt that they were unnecessary at times? Do you think that it has affected your development in any way?
All in all well done, and good luck on the last weeks of development,
Max Kassander.