This course presents the Scrum Framework to students and provides opportunities for the students to practice the process by executing a project using the Scrum Framework.
The first two days of this course are designed to present the student with an overview of the Scrum Framework and detail about the roles, ceremony, and artifacts utilized in Scrum led project. Subjects covered will include:
- Overview and Concepts
- Agile Overview
- Scrum Overview
- Sprints
- Scrum Planning
- Release Planning
- Sprint Planning
- Roles
- ScrumMaster Role
- Product Owner Role
- Team Member Role
- Self-organizing Teams
- Scrum Concepts / Disciplines / Coordination
- Self-organizing Teams
- Time-boxing
- Distributed Scrum
- Scaling Scrum
- Requirements
- Product Backlog Stories
- Proper Sizing of Product Backlog Stories
- Estimating (Hours vs. Story Points)
- Epics
- Definition of "Done"
- Ceremony
- Daily Standup Meeting
- Sprint Review
- Sprint Retrospective
- Artifacts
- TaskBoards
- Velocity
- Sprint / Release Burndown
- Burndown vs. Burnup
Students will focus on developing working software via labs during these next eight days. The format of the labs will simulate a real Scrum development cycle with one Sprint being performed each day. The daily cycle will also be reduced so that the students get exposed to multiple daily stand-up meetings as well. Students will be expected to define roles on their Scrum team, maintain the product backlog, maintain a Taskboard, calculate velocity, and develop working software that can be demonstrated.
- Each day will follow the same basic format... After some initial introduction to the project on Day 3 the students will build a Product Backlog. They will provide estimates and prioritization for the backlog stories. The remainder of the course will be creating the product defined by the backlog utilizing the Scrum Framework.
- Each day will represent a Sprint in the Scrum Framework. The students will be expected to hold a sprint planning meeting, execute 2 - 3 daily standup meetings, hold a sprint review, and hold a sprint retrospective during the day.
- In addition to the Sprint activities, each day the students will be presented with Object Oriented topics that are applicable to those days development activities. The lecture topics are listed below.
- Students will be expected to utilize Test Driven Development practices during all Lab activities.
- Students will be presented with problems that typically arise during a Scrum project such as Chickens Speaking during daily standup, team members missing daily standup, getting involved in technical discussions in daily standup, technical problems during the sprint, etc...
- The entire Scrum Framework activities will be addressed daily through the following cycle:
- Sprint Planning
- Students will perform a sprint planning meeting for each Sprint in order to review the stories, develop tasks, and establish the Taskboard for the Sprint.
- Sprint
- Each sprint will contain simulations for 2 to 3 working days. Students will participate in daily standup meetings and work on completing tasks that provide working software to complete the stories on the product backlog
- Sprint Review
- Students will hold a Sprint Review Meeting to demonstrate their working software to either the instructor individually or the class as a whole
- Sprint Retrospective
- Students will hold a Sprint Retrospective Meeting and identify things that worked well and things that could use improvement. They are expected to identify at least one item that could use improvement and focus on that item during the next Sprint
- Daily Wrap-up
