Academic Year Model Portfolio Assessment Type
2025 Collaborative 2 Individual Report
Development
(5CS024)
Report on Sprint 2nd as a
RentEase -Developer
Name: Aaditya Chaudhary Tharu
UID: 2414024
Tutor: Bhanu Aryal
Module Yogesh Bikram Shah
Leader:
Submission May 14th, 2025
date:
Self-appraisal form
Personal objectives—performance measurement
Acknowledgment
Self-appraisal form
Student number 2414024 Name Aaditya Chaudhary Tharu
Project RentEase (Rental Services) Date May 19th, 2025
Role Developer Team Group A
Sprint (1 or 2) Sprint 2
Personal objectives—performance measurement
Step 1 - Enter your agreed personal objectives at the start of each sprint (first column). These
should be copied from your role description.
Objectives Evidence provided Evaluation
(E.g. appendix A, file name, etc.) Student/tutor
Bug fixing At RentEase, I played a major role in user experience and 7/10 /10
usability, identifying and remedying different software and
interface problems. My duties involved correction of errors
in property views, repair of broken navigation, and
improvement of poor performance. Instead of bug fixes, I
worked on solutions to user authentication problems, and I
was putting the whole booking journey through very
intensive testing to ensure that it functioned well on all
devices in all usage contexts.
Tutor feedback:
Implementing I added a footer that provides direct access to essential 9/10 /10
functional sections such as “About Us, “Contact”, and “Privacy
requirements Policy”. In the listings management module, I developed
features that enable the property owners to manage their
listings, i.e., create, adjust, pause and to maintain them,
including ability to assign detailed descriptions & pricing. I
designed a feature through which tenants can search for
available houses, track their rental activity, view their
previous bookings and conveniently set the conditions of a
lease.
Tutor feedback:
Version Control I continued to work on my code contributions using Git, 13/15 /15
versioning control, in GitHub with the team. I was working
on authentication implementation, API development of
property listings, and frontend component design. Using
GitLab commit logs and graphs, one can see easy how my
code evolved and what tasks I joined in during the project.
Tutor feedback:
Commenting code Adding simple, informative notes inside the code to explain 3/5 /5
its purpose or purpose’s rationale or significance to all users
is called commenting. This habit improves understanding
for you and future you as well as the maintainability of your
code. Leave your comments on complex or tricky grounds,
and do not copy what is obvious in the code.
Tutor feedback:
/40 /40
Acknowledgment
It is a chance for me to thank my tutor, Bhanu Aryal who has continued to support during
sprint 2 of the RentEase project in the Collaborative Development module. Other than
developing my technical and teamwork skills on the base of what I have previously gained
during Sprint 1, I was working on my skills in the multicultural team during Sprint 2. We
remained rooted in the tools like Jira and GitHub; our tech stack: [Link], TypeScript,
PostgreSQL, [Link], Vercel and Cloudinary remained functional.
This sprint was another step towards the immersion into the Agile practices and server side
coding. The few stumbling blocks, like developing the search functionality, our productive
teamwork and team communication allowed us to develop rather well. I would be very much
thankful for the learning opportunity and, I would like to practice such skills in future sprints.
Evidence of good collaboration
Good communication and file sharing
Receivable evidence includes:
- Emails and other types of messages.
- Screenshots of conversations in which you actively participate.
- Screenshots showing files (designs, reports) that you shared with your team on Jira.
Important: Please include no more than 5 items
Communication was very important in our team based development process to keep the team
on target. We used a mix of communication forms based on the nature and urgency of a
message. Only formal updates and important announcements were mostly sent through email
so we can have some record of important information and decisions made. However, for
more immediate and casual communication we used such platforms like Discord, WhatsApp.
These instruments enabled timelier responses and made it possible for us to communicate in
real-time, particularly, when organizing and discussing tasks, and clarifications within
working hours.
I kept an engaged presence in our group discussions providing regular inputs regarding task
assignment, project goals and imaginative ideas. This open communication kept us in a
position to recognize challenges early and act jointly to create good solutions. Through the
discussions I could keep myself up to date and make sure my responsibilities were
corresponding with the team’s progress.
In the case of file sharing we used WhatsApp to send smaller documents such as design
drafts, screenshots or planning documents very quickly. To help us manage our code and
work as a team, we adopted version control instruments, such as Git, which enabled many
team members to work on different project portions without bringing conflicts. Such a system
both provided transparency and the ability to trace changes, roll back mistakes and keep the
workflow in a structured order. In total, our approach to communication and file sharing
made a sizeable contribution to the successful and collaborative nature of the project.
Continuing Personal Development (CPD)
Receivable evidence includes:
- Course/seminar attendance register
- Online course: certificate of completion
- Word document summarising what was learnt and how it can be used on the project
Important: Please include no more than 5 items
Although I did not attend formal courses or seminars during this project, I took a self-directed
approach to learning by relying heavily on online resources such as YouTube tutorials and
the W3Schools platform. These resources provided me with the flexibility to learn at my own
pace and focus on the exact skills needed for the successful development of our project.
While platforms like YouTube and W3Schools do not offer formal certificates of completion,
the practical, hands-on experience I gained from following their tutorials was highly valuable
and directly applicable to the technical challenges I encountered.
Through this self-paced learning, I focused primarily on backend development and
deployment processes, which were critical components of our web application. One of the
key areas I explored was the use of [Link], a powerful runtime environment that allowed me
to build a scalable and efficient backend for the application. Using [Link], I learned how to
create APIs that could handle HTTP requests, manage user data, and interact with the
database. I also familiarized myself with [Link], a web framework for [Link], which
simplified routing and middleware integration, ultimately speeding up development.
Another significant area of learning was PostgreSQL, a robust open-source relational
database system. I studied how to design and structure databases, create tables, set up
relationships between them, and execute queries to retrieve and manipulate data. This
knowledge was essential for ensuring that the application had a reliable and secure system for
storing and managing user information, content, and other data. Understanding PostgreSQL
also helped me write efficient queries and optimize the performance of the application by
reducing latency in data retrieval.
In addition to backend development, I explored deployment strategies to make the web
application accessible to users over the internet. I followed detailed YouTube tutorials on
how to deploy [Link] applications using platforms like Heroku and Render. These tutorials
guided me through configuring environment variables, connecting to the database in a live
environment, and ensuring that the deployment pipeline was secure and stable. By learning
about deployment, I was able to move the application from a local development environment
to a live server, where it could be accessed and tested by team members and users.
These technical skills significantly contributed to the success of our project. With a solid
understanding of how backend servers function and how databases are managed, I was able
to take responsibility for building and maintaining the server-side of the application. The
ability to deploy the application also made it possible to share our work with others for
feedback and testing, which is a crucial step in any real-world development process.
Overall, although I did not earn formal certificates, the knowledge and skills I acquired
through self-paced online learning were comprehensive and practical. They enabled me to
contribute effectively to the technical development of our project, solve problems
independently, and understand the underlying architecture of full-stack web applications.
This experience also encouraged a habit of lifelong learning and self-reliance, which are
essential traits for any developer working in the fast-evolving tech landscape.
Issue tracking
Receivable evidence includes:
- Screenshots of personal contributions to GitLab issues.
Important: Please include no more than 5 items
During the course of the project, I was actively involved in issue tracking and problem
resolution using several collaborative tools, including GitLab, GitHub Issues, and Jira.
These platforms helped our team organize tasks, monitor progress, and address bugs or
feature requests efficiently. On GitLab, I contributed by creating, updating, and resolving
issues, especially those related to backend errors and database inconsistencies. I also used
GitHub Issues when managing repositories hosted outside GitLab, ensuring continuity in our
tracking system. Additionally, Jira was used in the early planning phase to outline major
deliverables and assign roles.
To support communication and collaboration around issue tracking, we frequently held
Google Meet sessions. These virtual meetings allowed us to review current issues in real
time, discuss blockers, and assign tasks more effectively. They provided a space for quick
clarification and team alignment, which significantly improved productivity. I also used
email to share updates and summaries after meetings, ensuring that everyone remained
informed. Screenshots of my personal contributions to GitLab issues—including bug
tracking, comments, and code-related discussions—are available and provide concrete
evidence of my role in maintaining the project's workflow and ensuring successful task
completion.
Work to deadlines
No evidence required. Your tutor will decide whether you have worked to deadlines based
on various factors (team meetings, discussions with other team members, discussion with
client etc.)