Part I the Scrum Guide
Total Page:16
File Type:pdf, Size:1020Kb
Senior Project - Part I CSc 190-01 (Seminar 32218) Tu 8:00 to 8:50 AM, Benicia Hall 1025 CSc 190-04 (Seminar 32545) Tu 9:00 to 9:50 AM, Benicia Hall 1025 Spring Semester 2018 Course Instructor: Professor Buckley Office Hours Office: Riverside Hall 3002 Time TBD Phone: (916) 278- 7324 or by appointment Email: [email protected] Required Prerequisites: Senior status (90 units completed) WPJ score of 70+, or at least a C- in ENGL 109M/W Courses completed: CSc 130, CSc 131, and four additional 3-unit CSc upper division courses that fulfill the major requirements (excluding CSC 192-195, CSC 198, CSC 199) Catalog Description: The first of a two-course sequence in which student teams undertake a project to develop and deliver a software product. Approved project sponsors must be from industry, government, a non-profit organization, or other area. Teams apply software engineering principles in the preparation of a software proposal, a project management plan and a software requirements specification. All technical work is published using guidelines modeled after IEEE documentation standards. Oral and written reports are required. Lecture one hour, laboratory three hours. 2 Units Required Text: SCRUM: A Breathtakingly Brief and Agile Introduction, Chris Sims & Louise Johnson, Dymaxicon ©2012 (If not in the bookstore, available from Amazon) Required Text (link to document is on the Course website): The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game Jeff Sutherland & Ken Schwaber, July 2017 READINGS (links available on course website): Agile Manifesto and Guiding Principles Establishing Self-Organized Agile Teams Self-organizing Scrum teams – Challenges and Strategies Collaboration Skills for Agile Teams Use cases versus user stories in Agile development Death March, Edward Yourdon (excerpt) “You can’t make teams jell. You can hope they will jell… “ User Stories Applied: For Agile Software Development, Mike Cohn Chapter 1: An Overview Chapter 2: Writing Stories Course website: http://athena.ecs.csus.edu/~buckley/CSc190/CSc190.html COURSE EXPECTATIONS: Teams will be formed at the beginning of the semester and will remain intact for the duration of both CSc 190 and CSc 191. The number of members on each team will be set by the instructor. Each team is responsible for securing a project Client; with the Client and proposed project being approved by the instructor. Teams are expected to self-organize which will require cooperation and collaboration of all team members throughout the duration of the project (CSc 190 and CSc 191). See reading references above. Each team is expected to understand and apply “Agile Principles” and to do the work in accordance with the SCRUM methodology adapted for Senior Project use. See reading reference above. Once a project is secured, each team is expected to also collaborate with their project Client throughout the duration of the project. In collaboration with the project Client, the team will produce a project Charter Document that documents why the project is needed, the criteria needed to measure success throughout the project and what will be needed to ensure the project provides the client with the value expected. In collaboration with the project Client, the team will create and prioritize a Product Backlog Document (a high level list of everything that needs to be built or done to make the product owner’s vision a reality). The team’s Product Backlog Document will formally describe each of the required product features, a description of the users of each feature, and the needs/objectives of each user’s expected interaction with the feature (these interactions will be specified in the form of user stories). The Product Backlog Document will also contain the team’s estimates of the scope of work associated with each of the user stories associated with each feature. The team is responsible for providing professional quality documentation … both in content and design for all required documentation. The planning and actual work required during CSc 190 will be scheduled into a series of two-week “sprints”. At completion of each sprint, the team is expected to meet with the project Client to 1) review and provide the team with feedback on the increment of work completed at the end of the sprint, and to 2) create the plan for the work to be completed in the next sprint. At the end of each sprint, the team should review what was accomplished… what went well, what could have gone better, and what improvement(s) could be made in the next sprint. Required of all team members: To attend all the Tuesday seminars and all Faculty Adviser meetings Required To establish a bi-weekly, end-of-sprint meeting time with the team’s Client and ensure at least a majority of team members attend all scheduled Client meetings Required of the team: To self-organize, coordinate, collaborate and assess the work assigned during each sprint. To be responsible for the quality of work and the contribution of each team member. To meet with the project Client 1) to collaborate in creating and maintaining the Product Backlog, 2) to identify the acceptance criteria associated with each required feature and the user needs associated with each feature, 3) to review and update, as needed, the Product Backlog at the end of each sprint. To prepare and provide the Course Instructor and the team’s Faculty Advisor with the required/standard weekly status report. To be responsible for the preparing agendas and minutes for all Client and Faculty Adviser meetings. To establish a process for responding to whatever reporting is required by the project Client, the Faculty Adviser and the Course Instructor. END OF SEMESTER DELIVERABLES Project Charter Document Product Backlog Document Weekly Sprint Task Board Reports (included in a folder) Weekly Faculty Advisor meeting agenda and minutes (included in a folder) Bi-weekly Client Meeting Agenda/Minutes (included in a folder) GRADING Team 15% Weekly Sprint Task Board Reports completed and submitted on time 20% Assessments provided by the team’s Client (during and end-of-semester reports) 20% Assessments provided by the team’s faculty adviser 20% Quality and effectiveness of the information contained in the required documentation (the Project Charter and the Product Backlog documents) 15% End of semester assessment of teams: Weekly Sprint Task Board and Product Backlog Reports (included and organized in a folder) Weekly Faculty Advisor meeting agenda and minutes (included and organized in a folder) Bi-weekly Client Meeting Agenda/Minutes (included and organized in a folder) Team Member 10% Individual team member attendance / contribution at all required meetings. NOTE: Team members are expected to have effectively cooperated and collaborated throughout the project. Failure of any team member to do so can negatively affect the project and consequently the evaluation of ALL team members. If problems arise, the course instructor should be informed immediately. TUESDAY’S CLASS RULE: No laptops, phones, iPads, tablets (NONE!) (Those in non-compliance will be marked absent) ACADEMIC INTEGRITY: You are responsible for reading the Sacramento State policies on academic honesty found at http://www.ecs.csus.edu/wcm/csc/academic/academicintegrity.html .