SIT708 – Assessment 2
Sprint 1: Project portfolio & Application Progress
Worth: 30% of your grade (details in unit guide)
Due: Friday, Week 9, 5:00 pm Friday, Week 10, 5:00 pm (Hard Deadline)
Individual Portfolio and Project Progress
The Project Portfolio and SW application (which we refer to as the “outcome of Sprint 1”) is where you create your
notes about this entire unit, along with your mobile application, week by week. You will also demonstrate that you
have accomplished all of the required coding exercises (with screenshots as evidence). We have this Portfolio instead
of an exam, so keep in mind that you need to demonstrate your understanding equivalent to if you were sitting an
In the Portfolio, you will create a reflective summary of the class notes and answers to practical coding exercises for
every project topic from every week within our unit. You are required to present a written report on each week’s topic,
analyzing and discussing how the topic relates to developing your mobile system application. You will also include a
screenshot of the output of each week’s hands on exercise, along with the significant learning notes. Appropriate
formatting required. Note, this is due before the Project, because you must have covered all concepts to be able to
complete the Project. Thus, this earlier due date somewhat forces you to make sure you cover all theory + practical
labs before you can finish the Project.
Purpose and Tasks
The Portfolio is where you actually learn. It is the foundation of this entire unit. The science behind this is
as follows. Creating a personal summary is to request your brain’s neurons to essentially fire connectivity
and activate over new information. When listening alone, passive information comes in and will reinforce
or relate to existing information in your brain, but won’t form new memories on its own. Basically, your
brain says “oh yes, this information relates to what I already know about ABC, so XYZ is important”, and the
new information is never “saved” into your memory. Passive listening only reinforces existing knowledge.
By pressuring your mind to “create” something (e.g. written summaries), this process pressures your mind
to create and use new pathways in your brain related to the new information, thus encouraging them to be
permanent. This is the simplest way to get the information into our brains and have it stay there. So, this
exercise is for you. For many topics, you’ll find you’ll remember the topic for the entire trimester
without having to revisit your notes.
Structure of your Project portfolio
Marking Justification: A cover page detailing the grade you are aiming for, and evidence for each individual
• Week 1:
• Week 2:
• Week 3:
• Week 4:
• etc… up to week 9 only.
Submit the file to the Assessment 2 and your submission must include:
1. Project Portfolio pdf/word
2. Current stage of your Mobile application (zipped folder)
However, you must complete your work weekly (both theory summary with your lessons learned, and all
exercises completed). And each week, you’ll demonstrate and discuss the same file again with your practical
demonstrator for feedbacks (your document will grow larger each week you write in it). You are always
welcome to edit the previous weeks’ work at any stage.
Note: keep one single entire document (append each week’s new content into the existing single document
you keep for this Portfolio). Do not separate each week into its own document. Every time you update and
discuss the document, it should contain everything till date.
Criteria Pass Credit (pass criteria plus the
Distinction (Credit criteria
plus the following)
HD (Distinction criteria plus
Regular updates (Weekly) Up to date copy every week
for feedback from
demonstrator / Tutor
Completed all exercise for
Presentation Consistent styling, title page,
header, footer, heading
Uses Styles for all main
formatting. Close to
Can be used as a
when reading online or
with/without color printing.
Rich texting Mostly plain text Some bullets/lists/tables/
images to explain the idea
Mix of text (~30%), images
(~30%) and rich text (~30%).
Maximize clarity and white
space, High conciseness
Explanation Accurate spelling, grammar
Easy to understand examples
and explanations: pass the
document to undergrad
student they should be able
to learn from your report
Not only easy to understand
but simultaneously cover
enough details for a team of
developers to learn from it.
At a book level: Complete
printed quick guide to mobile
Summary Summarised all main points.
Completed every week’s
At least 500 words in length,
5 code snippets, linked to
previous weeks learnings.
Reflects critical thinking!!!
Few findings and answers.
Includes images, facts and
information you searched for
to answer questions or seek
more understanding that
wasn’t included in the unit
contents. Some curiosity
questions and research to
answer those problems.
Lecture notes summary
reads like a professional mini
book. Your document is
Exercises Decent attempt of three
Complete answers for three
Usefulness and learnings
from the exercises
Three complete exercises.
Usefulness and short
description lines in the code.
Project Progress List of tasks that you have
accomplished this week
List of tasks that you have
accomplished this week
(>100 words). List of your
plan for the following week
(>60 words). Project
SIT708 – Assessment 2