Communications

Office: 164-1022
Phone: 909-869-5289
E-mail: dhwang@cpp.edu
Office hours: CIS Faculty Office Hours

Course description

Application of the processes, methods, techniques and tools that modern enterprises use to develop information systems projects. Management of a comprehensive, team-based project development lifecycle. Client partnership and user experience; team collaboration and communication; documentation and oral presentations. Prerequisites: A grade of 'C' (2.0) or better in at least two electives in the Application Development track.

Expected outcomes

• Apply appropriate processes, methods, techniques and tools in system development.
• Manage effectively a comprehensive, team-based project.
• Maintain proper client partnership and user experience.
• Collaborate and communicate effectively in group work.
• Produce comprehensive documentation and conduct effective oral presentations.
  

Student Teams

In this class students teams are formed to develop real-world business applications through using Scrum as one of the most popular agile methodologies. Team members and their responsibilities are as follows:

Product Owner

• Be the liason between the client and the team.
  
• Responsible for the success of the outcome of the product delivered by the team.
• Make Business decisions of importance and priorities.
• Deliver the vision of the product to the team.
• Prepare the User Stories for the team of development.
• Validate the outcomes and test them for their quality.
• Communicate on a continual base with all Stakeholders, financiers and the team.

ScrumMaster

• Be responsible for ensuring the team lives agile values and principles and follows the processes and practices that the team agreed they would use.
• Establishing an environment where the team can be effective
• Addressing team dynamics
• Ensuring a good relationship between the team and product owner as well as others outside the team
• Protecting the team from outside interruptions and distractions.

Development Team

• Web master/documentation/training -- may be done by one team member. 
  
• Team progress should be updated at least weekly.
  
• Other team roles include systems analyst, programmer, database administrator, network analyst, etc.
  

Course Materials

• Required:
  Scrum For Dummies
  Layton
  ISBN: 9781119467649
  Edition: 2
  Copyright: 2018
  

Grading

• Project outcomes: 70%
• Documentation: 10%
• Presentation: 10%
• Peer rating: 10%
  

Schedule & Deliverables

Week	Deliverables
Week 1	Team formation, teammate introduction, discussion of available projects.
Week 2	Gather initial requirements on customer site Scrum Introduction
Week 3	Scrum Introduction Weekly Scrum meeting
Week 4	Weekly Scrum meeting Bi-weekly customer meeting-Test and show increment (Sprint)
Week 5	Weekly Scrum meeting Project Demo I
Week 6	Weekly Scrum meeting Bi-weekly customer meeting-Test and show increment (Sprint)
Week 7	Weekly Scrum meeting
Week 8	Weekly Scrum meeting Project Demo II
Week 9	Weekly Scrum meeting
Week 10	Weekly Scrum meeting Bi-weekly customer meeting-Test and show increment (Sprint)
Week 11	Weekly Scrum meeting
Week 12	Weekly Scrum meeting Project Demo III
Week 13	Weekly Scrum meeting
Week 14	Weekly Scrum meeting Project Demo IV
Week 15	Presentation
Week 16	Final Exam Time - all team members must be present. Turn in Final reports and Peer Reviews.