Hello everyone So today in class we had our first sprint! I was really excited to actually attempt a sprint, but it didn't go the way I thought it would. We played a game my instructor created called Scrum Hero. Scrum Hero takes the whole scrum process and turns it in to a D&D style game. I was really lost since I was new to the scrum/sprint process and I've never played D&D. We assigned a scrum master (Steve) and product owner (Shea) to oversee the sprint. Steve was in charge of the burn up/burn down chart and Shea was in charge of our backlog. We gave each user story a value in our poker planning session. We did that to organize our user stories according to how important they were. We took our user stories and formed teams around each user story. Each team gave each user story a time limit. each time you completed a task it was marked on the burn-down chart. Now, the game itself put a twist on the whole process. The "Dungeons Master" would randomly hand out cards to each team member to to throw you off. An example of this is I could only talk by singing for 5 minutes. At the end of the day the sprint was a epic fail. We lacked communication and had poor planning at the beginning. It was so bad Emil stopped us, told us we sucked, and sat us down for retrospectives. The point of the game was to show you how bad a sprint can go if you do it wrong. We failed fast and hard but I'm sure the next time we have a sprint we won't make the same mistakes.
So today in class we had our first sprint! I was really excited to actually attempt a sprint, but it didn't go the way I thought it would. We played a game my instructor created called Scrum Hero. Scrum Hero takes the whole scrum process and turns it in to a D&D style game. I was really lost since I was new to the scrum/sprint process and I've never played D&D. We assigned a scrum master (Steve) and product owner (Shea) to oversee the sprint. Steve was in charge of the burn up/burn down chart and Shea was in charge of our backlog. We gave each user story a value in our poker planning session. We did that to organize our user stories according to how important they were. We took our user stories and formed teams around each user story. Each team gave each user story a time limit. each time you completed a task it was marked on the burn-down chart. Now, the game itself put a twist on the whole process. The "Dungeons Master" would randomly hand out cards to each team member to to throw you off. An example of this is I could only talk by singing for 5 minutes. At the end of the day the sprint was a epic fail. We lacked communication and had poor planning at the beginning. It was so bad Emil stopped us, told us we sucked, and sat us down for retrospectives. The point of the game was to show you how bad a sprint can go if you do it wrong. We failed fast and hard but I'm sure the next time we have a sprint we won't make the same mistakes.
No comments:
Post a Comment