Reflection 2
This reflection is based on Gibbs’ (1988) Reflective Framework.
Description: This is the first time we’re using scrum methodology for a project which is focusing on delivering working small portions of the end-product. It is an essential learning for me as it requires tight interaction and communication between different stakeholders. There are two interesting scrum artefacts to me: product backlog and the stand-up meeting. Product backlog requires the team to split the whole product into little blocks of user stories and prioritizing them. As for stand-up meeting, it allows the team to communicate openly about the progress of development and to identify any constraints that are holding the team up.
Feelings: Overall, I feel …show more content…
Firstly, communication in the team is honest and open. We are able to honestly describe what we are struggling with and come up with a solution. I think I did well particularly in helping others to debug their code in pair programming. Pair programming has become an important tool for us in regards to solving the problems. We did not lose too much time on a single task thanks to it. Another good aspect is that I keep the team on track with regular checking on the team because that is one of my responsibilities as a scrum master. One area that I can improve on is better understanding of requirements and writing better user stories. Although we have improved in terms of writing user stories, but I feel like we can still improve on them. Furthermore, I feel like I could improve the architectural design of the app to make it easier to follow and provide better …show more content…
We were also lacking knowledge in the GUI part as we’ve mainly developed in console in the past. In the end, we were able to combine our knowledge of java with the new knowledge of android that we’ve just learnt. Even though there is still some pressure of having to get work done, comparing to other methodologies I’ve used previously, scrum is far less overwhelming. Also, one advantage of having iterations in scrum is that we can change the amount of work we want to do based on the experience we had. It enables more flexibility for us which is why I think is one of the reasons that it has become so popular in the
This reflection is based on Gibbs’ (1988) Reflective Framework.
Description: This is the first time we’re using scrum methodology for a project which is focusing on delivering working small portions of the end-product. It is an essential learning for me as it requires tight interaction and communication between different stakeholders. There are two interesting scrum artefacts to me: product backlog and the stand-up meeting. Product backlog requires the team to split the whole product into little blocks of user stories and prioritizing them. As for stand-up meeting, it allows the team to communicate openly about the progress of development and to identify any constraints that are holding the team up.
Feelings: Overall, I feel …show more content…
Firstly, communication in the team is honest and open. We are able to honestly describe what we are struggling with and come up with a solution. I think I did well particularly in helping others to debug their code in pair programming. Pair programming has become an important tool for us in regards to solving the problems. We did not lose too much time on a single task thanks to it. Another good aspect is that I keep the team on track with regular checking on the team because that is one of my responsibilities as a scrum master. One area that I can improve on is better understanding of requirements and writing better user stories. Although we have improved in terms of writing user stories, but I feel like we can still improve on them. Furthermore, I feel like I could improve the architectural design of the app to make it easier to follow and provide better …show more content…
We were also lacking knowledge in the GUI part as we’ve mainly developed in console in the past. In the end, we were able to combine our knowledge of java with the new knowledge of android that we’ve just learnt. Even though there is still some pressure of having to get work done, comparing to other methodologies I’ve used previously, scrum is far less overwhelming. Also, one advantage of having iterations in scrum is that we can change the amount of work we want to do based on the experience we had. It enables more flexibility for us which is why I think is one of the reasons that it has become so popular in the