Syllabus: ESOF 423
Related: Course Overview
Spring 2023
Note: dates and assignments more than a week out may be adjusted as the semester goes on. Please consider this page to be a living document subject to changes througout the semester.
|
Week |
Date |
Topic |
Notes |
Projects |
|
1 |
W Jan 18 F Jan 20 |
CourseOverview, Introductions Agile Development, Scrums |
Students to introduce themselves
|
Meet others in the class; get an idea of who you might like to work with
|
|
2 |
M Jan 23 W Jan 25 F Jan 27 |
Client pitch 1: Mr. Dylan Gillespie preparing for projects Client pitch 3: Dr. Philip Bain |
Clients pitch projects to class |
Listen to client pitches; ask questions; decide which project you'd like to develop
|
|
3 |
M Jan 30 W Feb 1 F Feb 3 |
Client pitch 2: Mrs. Keri Hallau Group/Project Choices, Artifacts lab |
Choose projects, groups |
Form groups Sprint 0: Planning Scrum |
|
4 |
M Feb 6 W Feb 8 F Feb 10 |
lab (clients invited to attend) Local Development, Version Control lab |
|
Scrum Lecture Sprint 0 review; ZFR |
|
5 |
M Feb 13 W Feb 15 F Feb 17 |
GitHub, Documentation lab lab |
|
Lecture Sprint 1 Planning Weekly Scrum |
|
6 |
M Feb 20 W Feb 22 F Feb 24 |
PRESIDENTS DAY - No classes lab lab |
|
Weekly Scrum Sprint 1 review |
|
7 |
M Feb 27 W Mar 1 F Feb 3 |
Continuous Integration lab lab |
|
Lecture Sprint 2 Planning Weekly Scrum |
|
8 |
M Mar 6 W Mar 8 F Mar 10 |
Black box testing lab lab |
|
Lecture Scrum Sprint 2 review; Beta release |
|
9 |
March 13 - 17 |
SPRING BREAK |
No classes
|
|
|
10 |
M Mar 20 W Mar 22 F Mar 24 |
lab Unit testing lab |
|
Sprint 3 Planning Lecture Scrum |
|
11 |
M Mar 27 W Mar 29 F Mar 31 |
Guest Speakers: Marrissa & Chris lab lab |
|
Lecture Scrum Sprint 3 review; Portfolio Draft |
|
12 |
M Apr 3 W Apr 5 F Apr 7 |
lab lab UNIVERSITY DAY - No classes |
|
Sprint 4 Planning (No Lecture) |
|
13 |
M Apr 10
F Apr 14 |
Software and Web App Testing (recording: D2L); Guest visitor Maryann Cummings to meet with groups - please demo projects with a focus on testing. lab lab |
|
Lecture (online) Scrum Sprint 4 review; FCR |
|
14 |
M Apr 17 W Apr 19 F Apr 21 |
User Testing, TDD/PP lab lab |
|
Lecture Sprint 5 Planning Scrum |
|
15 |
M Apr 24 W Apr 26 F Apr 28 |
Code Reviews, APIs lab lab |
|
Lecture Scrum Sprint 5 review; Release candidate |
|
16 |
M May 1 W May 3 F May 5 |
Dylan: Groups 1, 2 (Mach) Philip: Groups 4, 5 (DxMood) Keri: Group 3 (BSF) |
Presentations Presentations Presentations |
Final Release, Portfolio due |
|
Finals Week |
M May 8 |
No final exam - Use for exam period for presentations if more time is still needed. |
|
|
Meetings
- Monday, Wednesday, Friday from 1:10 pm - 2:00 pm in Roberts Hall Room 210.
Instructor
- Mr. Daniel DeFrance
- Office hours
- Office: Barnard Hall 358
- E-Mail: daniel.defrance@montana.edu
Course Assistants
- TBD
- Availability for Assistance: TBD, and by appointment.
- Location: Barnard Hall 259
- Email:
Course Policies
No cheating - The work you submit to be graded must be your own.
No late assignments - Assignments submitted after the due date will not receive credit. Please plan accordingly.
Medical emergencies - If there is a medical emergency, tragedy or sudden hardship, you will need to provide written confirmation in order to have consideration for an exception to any grading schedules.
Additional Course Information
Grading
Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade.
- Assignments: 40%
- Project Sprints: 30%
- Sprint planning meeting outcomes
- Scrum meeting participation
- Work done toward achieving the defined sprint goal
- Proper maintenance of the scrum artifacts (burn down charts and updated product backlog)
- Activity and maintenance of the git workflow and the repository.
- Product releases – 20%
- Will be divided among the intermediate releases. Completed requirements, application of design patterns and refactoring, code maintainability/extensibility and quality assurance methods, continuous integration, testing, and delivery.
- Final release presentation + Portfolio – 10%
- Presentation content: high level UML diagrams displaying the design, discussion on the design patterns used, discussion of code maintainability/extensibility and methods used to accomplish them, quality assurance methods and their evaluation.
At the end of the semester, grades will be determined (after any curving takes place) based on your class average as follows:
- 93% and higher: A Excellent quality and intellectual initiative
- 90% and higher: A-
- 87% and higher: B+ High quality and intellectual initiative
- 83% and higher: B
- 80% and higher: B-
- 77% and higher: C+ Acceptable quality, satisfactory achievement
- 73% and higher: C
- 70% and higher: C-
- 67% and higher: D+ Deficient quality, did not meet minimum requirements
- 63% and higher: D
- Otherwise: F
Additional MSU Resources
Copyright Notice
This syllabus, course lectures and presentations, and any course materials provided throughout this term are protected by U.S. copyright laws. Students enrolled in the course may use them for their own research and educational purposes. However, reproducing, selling or otherwise distributing these materials without written permission of the copyright owner is expressly prohibited, including providing materials to commercial platforms such as Chegg or CourseHero. Doing so is in violation of U.S.copyrightlaw as well as MSU’s Code of Student Conduct.
Copyright © 2023 Montana State University and Daniel DeFrance