Scribd
Upload
9 views

Its120l Project Outline

The document outlines a timeline for a project involving the development of a functional application, detailing phases from planning to presentation. Key deliverables include a project proposal, requirements analysis, system design, coding iterations, and a final presentation. Each phase includes specific tasks, acceptance criteria, and documentation requirements to ensure compliance with Agile methodology.

Uploaded by

Yuri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

Its120l Project Outline

The document outlines a timeline for a project involving the development of a functional application, detailing phases from planning to presentation. Key deliverables include a project proposal, requirements analysis, system design, coding iterations, and a final presentation. Each phase includes specific tasks, acceptance criteria, and documentation requirements to ensure compliance with Agile methodology.

Uploaded by

Yuri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Timeline

Weeks 5-6: Planning


- Project Conceptualization
- Define scope and limitation (must have CRUD [create read update delete tasks],
must have login and registration)
- DELIVERABLES: Proposal, Requirements Analysis, Sitemap, Sprint Planning

Week 7: Design
- Implementation: Sprint Iteration 1 - System architecture and UI
- ERD
- Prototype - UI
- Acceptance Criteria
- TO PASS: Prototype, ERD, Acceptance Criteria

Week 8:
- Implementation: Sprint Iteration 2 - Coding
- Weekly Scrum minutes of the meeting
- GitHub Link of progress
- TO PASS: Minutes of the meeting, GitHub progress
Week 9:
- Implementation: Sprint Iteration 2
- Weekly Scrum minutes of the meeting
- GitHub Link of progress
- TO PASS: Minutes of the meeting, GitHub progress
Weeks 10-11:
- Implementation: Sprint Iteration 3
- Weekly Scrum Minutes of the Meeting
- Github of Progress
- TO PASS: Minutes of the meeting, GitHub progress
Weeks 11-12
- Implementation: Sprint Iteration 4
- Presentation of Project
- GitHub link of progress + README of how to setup and run program
- Acceptance Criteria Results - showing that the acceptance criteria was
implemented
- TO PASS: GitHub repository, Acceptance Criteria Results
Weeks 5-6 : Planning Deliverables
1. Project proposal
For the term project, students must develop a functional application (web,
mobile, desktop, etc.) that caters to a business need. They have the discretion to
choose the business and determine the scope of their application, but must keep
in mind the timeline for the project. Students may also choose their own tech
stack with the limitations of tools to be discussed.

Contents of the project proposal:


● Background of the application and business: discuss the business that the
application is catered to. Discuss how the website will help improve
business processes.
● Products and services offered by the business: discuss the details of the
products and services offered and details of the processes by the
business
● Features: List down the features of the website and give an overview of
the proposed content
● Sitemap: Create a diagram that shows the hierarchy of viewing the
application. Example can be found here.

2. Requirements Analysis
Clearly defining requirements and scope of the project allows to set expectations
and removes confusion on what to do.

Contents of the requirements analysis


● Business objectives: list at least 3 objectives for the business in setting up
the project (how would the project benefit the business?)
● User requirements: for each feature of the project, list down what the user
can do in the software, and what it achieves for the business. A common
format:
The [user type] shall [interact with the software] in order to [meet a
business goal or achieve a result]
● Functional requirements: For each feature, explain what it should
accomplish, and what the users and system should do and comply with.
Example can be found here.

You may use this site for more information about requirements analysis.
3. Sprint planning
Sprints are part of the Agile methodology for Software Engineering. Students
have to plan five iterations of sprints and must comply with the timeline set.
Each sprint should have certain tasks to finish, in the period of 1 week.

Contents of the sprint planning document:


● For each sprint, assign a task for each member. The task must be
accomplished within the sprint, and assigned to one member.
● Example can be found here.

Notes: pass the requirements in one whole document.


Week 7: System and UI design
This week is meant to guide the entire coding implementation and be referenced
throughout the whole project.
1. Prototype
Create a prototype using Figma. This prototype is supposed to be the guide in
implementing the UI of the system. Create a page for each feature and a
separate screen for each function. Example can be found here.
2. ERD
This would be used as a reference when creating your database. Every team
member should follow the naming conventions and relationships so there are no
problems with query. Example can be found here.
3. Acceptance Criteria
This is a checklist of what should be done on a process of the system. This will
be used to check how well your system complies to requirements. Example can
be found here.

Note: pass all deliverables in one whole document. Please provide a link to the Figma
project.
Weeks 8-11: Coding implementation
In these weeks, you will be implementing the system based on the deliverables
submitted in the previous weeks. You will be required to meet once a week (called a
scrum) in compliance of Agile methodology.

Specifically, the scrum should include:


● The list of tasks done for the previous week
● The list of tasks to be done in the next sprint
● Any difficult tasks and bugs that hinders progress

This usually only takes 15 minutes, unless there are important matters to address (such
as the last bullet point). Note: it is not necessary to wait until the weekly scrum to
address any blockers. Request help if you are truly stuck.

1. Weekly scrum minutes of the meeting


For each member, list down the tasks done and the tasks to be done this week.
At the end of the document, copy the sprint planning table and add a column to
the right. Put in the status of the task as NOT STARTED, ON GOING, or
COMPLETED.
2. GitHub link of progress
Add the GitHub link of your repository. Add the screenshot that the changes
made that week has been made and merged into the main branch.

Week 11-12: Presentation


You will be presenting the system live.

Other deliverables:
1. Acceptance criteria compliance
Copy the Acceptance criteria document. Format it into a table, and another
column to the right. Put the status in as COMPLIED if it was implemented.
2. GitHub README
The README in your GitHub repository should dictate how to set up your
application to the local environment.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy