Discuss and reflect on tracking your Project Progress using Scrum (25%)

Discuss and reflect on tracking your Project Progress using Scrum (25%)

Discussion (400 words):

You should reflect on what you have learnt from using the Scrum process and Scrum template and discuss how this will be useful to you in future projects. 133

I created user stories that could not be closed during one sprint. Since the concept of acceptance criteria was not clear, it resulted in a lot of wastage of time during sprint meetings since each of us in the team had our own ideas of how the final product would look like. I learned to not accept a user story without the acceptance criteria to save unnecessary time on sprint. Also, the concept of done was not clear since there were bugs that resulted even after code review. So, does done really means done? Since, after evaluating and realizing what could have improved, I feel in the future projects I would have a head start and not repeat the mistakes I made this time.

• You should also evaluate the effectiveness of using the scrum process as a framework to manage and developed your client-based project. 133

Scrum process enables the development team to have early inspection along with analysis at the end of each sprint to avoid failures in front of the client. In this way the issues that have been recognised or the new input given by the client are quickly implemented. This will avoid failure at the end of the project. There is open communication between the development team and the client which ensures that the output being given is implemented. Moreover, Scrum plays a role in the establishment of the transparency through each sprint meeting of the product, the client knows what to expect.Also, weekly meetings with the client makes the client aware of the progress of the product and give inputs which boosts the morale of the team. Thus, both works together to ensure the success of the project.

• You can also discuss what is the difference and similarity between Agile methods and Design Thinking. 133

Differences:

Agile requires commitment from the client, but design thinking teaches you how to do it. Design thinkingmethod should show you how to listen to customers and analyze their actions so that you can understand their needs and recognise the issues that need to be solved.Agile teams will speak to end users on a daily basis, but if they don’t have the ability to listen and respond to their needs, it won’t add the value to what they are looking for. Also, Design thinking is about finding the right problem to solve however agile is about solving the already defined problems. Also, Design thinking can be used to solve any complex issue with no certainty about the solution however agile is a project management tool for creating better software.

References:

https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/

https://designthinking.ideo.com/

• An interesting and insightful critical evaluation has been provided which clearly shows the effectiveness of the Scrum Process and Template in helping the team address to manage and develop your client-based project.
• You provide interesting points on the similarity and difference between Agile and Design Thinking
• Provides an interesting and insightful reflection of what you have learnt with an excellent discussion on how this will be useful in future projects.
• You included excellences references in your discussion.

Task 2b – Reflecting on the Use of Code Review to Improve Code Quality (20%) Reflect on what you have learnt from carrying out code reviews to improve the quality of code for your project (400 words):

• You should include two reflective examples to show where you have carried out a review of code submitted by another team member and your review comments have helped your team member to make a change to improve code quality.
• You should include two reflective examples of where you have submitted code for review by another team member and the team member’s comments have helped you to make a change to improve code quality

Provide the appropriate code fragments of before and after to help illustrate how the code is of a higher quality than it was before. The number of words doesn’t include the code fragments (this could be also screenshot of the code).

An interesting and insightful reflection was provided on what you had learnt from carrying out code reviews