Collaborative Software Development with Western University Students
Timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
-
January 18, 2025Sprint 0
-
February 1, 2025Sprint 1
-
February 15, 2025Sprint 2
-
March 1, 2025Release 1 - MVP
-
April 9, 2025Experience end
Timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
On the week of Oct. 21st, the client is to provide a problem statement, any supporting documents and a presentation to introduce the project to the students and answer their questions. The students will be working on the initial requirements analysis until the end of the fall semester.
-
January 18, 2025Sprint 0
The winter term starts on Jan 6th, before then the course instructor will work with the client to prioritize the set of requirements to make sure the students focus on the most important requirements first.
The first 2-week sprints, the students will work on refreshing/reviewing the initial requirements, set-up the development environment, and create the Mockups/Wireframes for feedback.
-
February 1, 2025Sprint 1
The first shippable increament.
-
February 15, 2025Sprint 2
Second Shippable increment.
-
March 1, 2025Release 1 - MVP
First deployed release. MVP with all the must-haves implemented.
-
March 15, 2025Sprint 3
Third shippable increament
-
March 29, 2025Sprint 4
Final increment.
-
April 5, 2025Final Release
Final deployed release with the should-haves implemented and possibly the nice-to-haves for bonus.
-
April 9, 2025Experience end
Categories
Website development Mobile app development Software developmentSkills
effective communication software development life cycle scrum (software development) communication constructive feedback agile methodology project management software engineering computer engineering teamworkWestern University’s Faculty of Engineering offers a unique opportunity for employers to collaborate with third-year Software Engineering students enrolled in SE 3350B: Software Engineering Design I. In this course, students learn to apply the software development life cycle using the Scrum framework, focusing on teamwork, Agile methodologies, and effective communication. Through this experience, learners aim to build skills in project management, problem-solving, and software development while delivering valuable solutions to real-world challenges.
Client participating in this experience is expected to maintain regular communication with learners, provide necessary project information, and be present during the final presentation. Constructive feedback will be crucial in helping students refine their work and gain insights into professional practices.
Approximately, 40 - 50 hours of commitment throughout the project is needed for feedback and Q&A sessions.
At the end of the project the client is to rank each of the projects in a scale of 1 - 5, and choose the one they wish to take for implementation, and the students are to provide the source code and the documentation of the project.
Project timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
-
January 18, 2025Sprint 0
-
February 1, 2025Sprint 1
-
February 15, 2025Sprint 2
-
March 1, 2025Release 1 - MVP
-
April 9, 2025Experience end
Timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
On the week of Oct. 21st, the client is to provide a problem statement, any supporting documents and a presentation to introduce the project to the students and answer their questions. The students will be working on the initial requirements analysis until the end of the fall semester.
-
January 18, 2025Sprint 0
The winter term starts on Jan 6th, before then the course instructor will work with the client to prioritize the set of requirements to make sure the students focus on the most important requirements first.
The first 2-week sprints, the students will work on refreshing/reviewing the initial requirements, set-up the development environment, and create the Mockups/Wireframes for feedback.
-
February 1, 2025Sprint 1
The first shippable increament.
-
February 15, 2025Sprint 2
Second Shippable increment.
-
March 1, 2025Release 1 - MVP
First deployed release. MVP with all the must-haves implemented.
-
March 15, 2025Sprint 3
Third shippable increament
-
March 29, 2025Sprint 4
Final increment.
-
April 5, 2025Final Release
Final deployed release with the should-haves implemented and possibly the nice-to-haves for bonus.
-
April 9, 2025Experience end
Project Examples
This experience is designed for projects that allow students to leverage their knowledge and skills in a practical setting. Ideal projects should involve the development of innovative software solutions that align with the needs of the employer.
Project Examples:
- Web Application Development: Create a user-friendly web application to enhance customer engagement for a local business.
- Mobile App Prototype: Design a prototype for a mobile application that addresses a specific community issue, such as health or transportation.
- Software Tool for Efficiency: Develop a tool to streamline internal processes for an organization, increasing productivity and reducing manual tasks.
- E-commerce Platform Enhancement: Improve an existing e-commerce platform by adding features that enhance user experience and boost sales.
- Data Analytics Dashboard: Build a dashboard for visualizing key performance metrics for a business, enabling better decision-making.
Companies must answer the following questions to submit a match request to this experience:
What resources or information will you provide to support the students’ work?
What specific software development challenge do you want students to address?
Timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
-
January 18, 2025Sprint 0
-
February 1, 2025Sprint 1
-
February 15, 2025Sprint 2
-
March 1, 2025Release 1 - MVP
-
April 9, 2025Experience end
Timeline
-
October 22, 2024Experience start
-
December 7, 2024Initial Requirements & Architecture Design
On the week of Oct. 21st, the client is to provide a problem statement, any supporting documents and a presentation to introduce the project to the students and answer their questions. The students will be working on the initial requirements analysis until the end of the fall semester.
-
January 18, 2025Sprint 0
The winter term starts on Jan 6th, before then the course instructor will work with the client to prioritize the set of requirements to make sure the students focus on the most important requirements first.
The first 2-week sprints, the students will work on refreshing/reviewing the initial requirements, set-up the development environment, and create the Mockups/Wireframes for feedback.
-
February 1, 2025Sprint 1
The first shippable increament.
-
February 15, 2025Sprint 2
Second Shippable increment.
-
March 1, 2025Release 1 - MVP
First deployed release. MVP with all the must-haves implemented.
-
March 15, 2025Sprint 3
Third shippable increament
-
March 29, 2025Sprint 4
Final increment.
-
April 5, 2025Final Release
Final deployed release with the should-haves implemented and possibly the nice-to-haves for bonus.
-
April 9, 2025Experience end