I have just been through the worst Sprint Review Meeting (Scrum). We didn’t communicated with Product Owner very well and the demonstration is terrible. However, it is a good learning process and I want to summarize about what I have learned.
Scrum is all about transparency and communication. The first reason we failed this sprint is we failed to communicate with client. We did something we thought was awesome stuff which didn’t get approved from client before we started. So we gave a big “surprise” to client in the sprint review meeting. So, instead of showing all the User Stories to PO in the sprint review meeting, we need to keep the PO posted during the sprint. Let him/her have a general idea regarding what we are doing to avoid misunderstanding and surprise in sprint review meeting. I suggest if we have one week sprint, we need give PO an update every day. If two weeks sprint, give PO an update every two days etc.
Also, Paul gave me a good example about how to demonstrate a User Story in an efficient way. First,use a few short sentences to quickly show what we missed (the reason of creating this user story) and what we have done to fix these issues for the User Story. The most important point is people prefer to see the demo, to see have the code runs instead of listening someone keep talking all the time, so we need to be general in describing the User Story and focus on demonstration. Also when you show the demo, please don’t hesitate to tell everyone what are you doing now.
Any comments are welcome.
No comments:
Post a Comment