Senior Project - Part II CSc 191-01 (Seminar) Th 8:00 to 8:50 AM CSc 191-04 (Seminar) Th 9:00 to 9:50 AM PREVIEW http://athena.ecs.csus.edu/~buckley/CSc191/CSc191.html

READINGS (links on course website): The Scrum Guide: The Definitive Guide to Scrum… Sutherland and Schwaber, July 2017 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…”

(See reading references above) Course expectations Teams are expected to self-organize, which requires the cooperation and collaboration of all team members throughout the duration of the project. (See reading references above) Each team is expected to also collaborate with their project client throughout the duration of the project. Each team is expected to apply the “Agile Principles” and to organize and do the work in accordance with the SCRUM methodology as presented in class. The planning and all actual work during CSc 191 is to be scheduled into a series of two-week sprints.

Course expectations In collaboration with the project client, the uncompleted prioritized Product Backlog features and stories are to be reviewed (and re-prioritized if needed) prior to the team selecting the amount of work they estimate can be completed in the next two week sprint. The objective of each sprint is to “complete” the design and development work associated with each of the Feature Stories included in the Sprint Backlog. “Complete” means that the design and development work has been fully tested and successfully integrated. Work not “complete” is to remain in the Product Backlog until it is selected for a future sprint and “completed”.

Course expectations At the end of each Sprint the team is to meet with their client to demonstrate the go live ready work completed. The work completed should be assessed. Suggested client changes should be discussed and if agreed to, these changes should be prioritized and inserted into the Product Backlog as new work. In addition, the team and project client should select the work to be undertaken in the next sprint. This means reviewing the uncompleted prioritized Product Backlog… agreeing on how much new work the team estimates that can be placed in the Sprint Backlog and completed in the next two week sprint.

Course expectations Upon completion of the project, the team is responsible for providing their client with the following documentation: System Test Report Maintenance Manual Again, the team is responsible for providing professional quality documentation … both in content, layout and design. The project must be completed, delivered and accepted by the client on or before the last day of instruction

Course expectations Required of all team members: To attend all the Thursday seminars and all Faculty Adviser meetings Required To establish bi-weekly, end-of-sprint meeting times 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 ensure that the team understands the objectives associated with each user need associated with each feature 3) To identify the acceptance criteria associated with each required 4) To review and update, as needed, the Product Backlog at the end of each sprint.

Required of the team To be responsible for the preparing agendas and minutes for all Client and Faculty Adviser meetings. To prepare and provide the Course Instructor with the team’s weekly Faculty Advisor meeting agenda (and minutes from the previous meeting) and the team’s weekly updated Task Board. To establish a process for responding to whatever reporting is required by the project Client, the Faculty Adviser and the Course Instructor.

GRADING It is important to know the following: “… the grade of A: Exemplary achievement of the course objectives. In addition to being clearly and significantly above the requirements, work exhibited is of an independent, creative, contributory nature... the grade of B: Superior achievement of the course objectives. The performance is clearly and significantly above the satisfactory fulfillment of course requirements… the grade of C: Satisfactory achievement of the course objectives. The student is now prepared for advanced work or study.” (Reference: CSUS Definition of Grade Symbols; – CSUS 2017-18 Catalog).

(during and end-of-semester feedback) Team 15% 20%   Team Member 10% Weekly team status reporting Assessments provided by the team’s client (during and end-of-semester feedback) Assessments provided by the team’s faculty adviser Quality and effectiveness of the information contained in the required documentation (the System Test Manual, Maintenance Manual, and User Manual) End of semester assessment of team’s: Weekly updated Sprint Task Board and Product Backlog Reports (included and organized in a folder) Weekly Faculty Adviser meeting agenda and minutes (included and organized in a folder) Bi-weekly Client Meeting Agenda/Minutes (included and organized in a folder)    Individual team member attendance at all required meetings (excused absences approved by Course Instructor)

NOTE ALL Each team member is expected to have participated and to have effectively cooperated and collaborated with all team members throughout the project. Failure of any team member to do so can negatively affect the project and consequently the evaluation of all team members. The requirement that each team “self organize” means that the team is responsible for ensuring that all team members are effectively participating throughout the life of the project. If problems arise, the course instructor expect to be informed immediately!

THURSDAY’S CLASS RULE A REPEAT No laptops, phones, iPads, tablets … (NONE!) (Those in non-compliance will be marked absent)

Credit Hour Policy Course Type   Course Type Typical Number of Student Hours in Class (weekly per unit) Typical Number of Student Preparation / Activity Hours Out of Class per weekly unit Minimum Total Hours per Unit Number of Semester Credit Hours Earned across 15 weeks Lecture, seminar, discussion, recitation 1 hour 2 hours 3 hours Weekly 1 unit Activity supervised as a group (laboratory, field trip, practicum, group studio, physical education) 2-3 hours 0-1 hour

Credit Hour Policy