CS 250 Agile Team Charter Macklin
.pdf
School
Southern New Hampshire University**We aren't endorsed by this school
Course
CS 250
Subject
Computer Science
Date
Dec 16, 2024
Pages
1
Uploaded by PrivateIceApe35
CS 250 Agile Team Charter Template To complete this template, replace the bracketed text with the relevant information. SNHU Travel Agile Team Charter Item Response Business Case/Vision (value to attain) The SNHU Travel project intends to develop a web-based travel booking platform that offers personalized travel packages to customers while providing a seamless user experience. Mission Statement (result to accomplish) The mission of our team is to deliver high-quality software products in a timely manner while ensuring satisfaction of all clients by maintaining our own agile principles, creating a collaborative environment and making a continuous effort to improve our development practices. Project Team (team members and roles) Christy (Product Owner), Amanda (Client), Ron (Scrum Master), Brian (Tester), and Nicole (Developer). Success Criteria Start date: 09/22/2024 Expected completion date: 10/27/2024 Final deliverable: Fully functional and tested travel booking website with personalized vacation packages. Key project objectives: 1 –Develop a platform that is user-friendly for booking vacation packages. 2 –Add in features that allow clients to have full customization for their vacation packages. 3 –Test the platform to ensure that it is fully functional. Key Project Risks Some of the main issues we expect to potentially run into are 1 –technical issues that could delay our project deadlines. 2 –Changes in the potential features of the travel booking platform. 3 –Maintaining understanding and communication amongst the project team. Rules of Behavior (values and principles) Professionalism, honesty and communication will be the founding principles of our project team. It is expected that all members work effectively and collaborate to ensure success as a team. Any issues amongst each other must be addressed professionally and respectfully. Communication Guidelines (scrum events and rules) -Sprint planning will occur on a regular basis -Daily scrum meetings every day at 11:30 am -Sprint reviews will be held at the end of each sprint -Sprint retrospective will be held at the end of each sprint -Backlog refinement will be handled by the product owner -Members of the project team will communicate updates on the project daily by use of email
