CS 250 Final Project

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

CS-250

Subject

Computer Science

Date

Apr 3, 2024

Type

docx

Pages

5

Uploaded by KailahWhitted_

Report
CS 250 Final Project Kailah Whitted Southern New Hampshire University Professor Konishi February 22, 2024
Sprint Review And Retrospective We finally completed another sprint and delivered another great product! As normal, the team will gather for a Sprint review and retrospective. During our meeting, we will talk through what worked and what didn’t, what we could do better on, and create a plan on what we need to next after to making necessary changes etc. The Scrum Master role is very straight forward, I make sure to be of help or give guidance to all members of the team and push the sprint forward. The most helpful exercised were daily check-ins/stand ups with the team, this allows for a open safe place for everyone to voice their comments, questions, and concerns about any issues or problems that may arise and lastly develop solutions and push the team forward. During these meetings, we also talk about what is going well and give credit where its due. This also helps keep open and healthy dialogue with the team. We also have Scrum board that available to the whole team along with a a software program that allows us to always track our progress. The Product Owner role is to collect value information from our clients about our product through focus groups and meetings. As the team made developments, the product owner reviews them with the team and discusses all questions, comments, and concerns. At times, the features would need to be modified due to trend changes and goals. The Product Owner then meets with the developers to talk
about the changes we had to make. For example, one change was to switch from just a basic travel level to a website that focused on wellness retreats and vacations. The change was brought to our potential clients first and the product owner brought a list of features that the users would want to see. Then the product owner and the developer reviewed the necessary changes before adding it to the backlog. In the end, we we’re all able to submit a quality product that met all the client’s needs. The Developer Team worked very hard to achieve the goal of making a solid software program. They worked very closely with our testing team and we’re both able to fulfill the goals of The Product Owner within the allowed time of the sprint. The Testers continue to give back feedback in a timely fashion to the Developers, which helped them work out bugs and improve the code. As user’s continued to give continuous new requirements for the wellness vacations, the Developers were able to keep adjusting to the client’s needs and with the help of the Testers creating new test cases for each new feature. In the end, the Developer Team gave the final working product to the Product Owner at the end of the sprint. The user stories, were always made available for the team and these stories helped the team the prioritize the client’s needs. The team was able to prioritize which items might take longer and have enough time to complete everything during the sprint. Due to the Agile approach to development, the team was also
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
able to complete all the lower priority items within the allotted time. Lastly, with the consistent feedback during mid-sprints, the team was also able to make the necessary changes to complete a finished product to meet the user’s needs. We used the Agile method to develop this product, it’s way more involved than the “waterfall” method, this really showed when the Product Owner would come back with changes based on the feedback from our users. The team was able to meet the user’s needs fast and efficiently, without effecting the sprint. The product backlog was also able to be updated with the new changes, if we had used the waterfall method this would have been put off until the final product was created. As the Scrum Master, communication was key at the end of the day to complete a final and efficient product. We had various forms of electronic communication, like emails, slack, video chats, etc. to delivery feedback to the team as quickly as possible and ensure everyone was on the same page while meeting our goals. Daily meetings, helped keep everyone together and made sure the team’s needs we’re also met. This was all open communication so everyone could voice their questions, comments, and concerns. We also a centralized board along with our online tools to everyone had access no matter where they were and as the Scrum Master, I could get feedback to them quickly. We had a lot of positive and some negative details to an agile approach to the software. The agile method enacts and encourages a self-sufficient team unlike the
waterfall approach. This helps the team have control over their role and makes for a more coordinated team. A lot of people aren’t content when there’s not a clear leader. The Scrum Master, however, is a leader and jack-of-all-trades but the team is created to work without a leader. Although, the Scrum Master delivers a lot of information to the team, the team also has to communicate information with each other to make the team run efficiently. Finally, the agile approach was the best approach for the SNHU Travel Website project because the team was able to make quick and efficient changes as the user’s brought feedback to the Product Manager. The travel site needed a lot of different features to be created. From the user stories, the Developers we’re able to work on them during a sprint and get necessary feedback to tester’s and back to the user’s to complete a final product. The Developer’s we’re able to have quick turn around times and get the necessary features added to complete the client’s needs. If we had used the waterfall method, we wouldn’t have been able to meet the time constraints due to having to revise certain features. The ability to work quickly and on the needs immediately help us keep progressing the project further.