Individual Contribution: Tausif Rahman

By

During Week 6, I focused on coordinating the group’s progress and keeping our work structured. I created the shared Google Doc we used for collaboration, organising it according to the brief and dividing each section by word limit so everyone could contribute efficiently. I also helped plan our workflow and timeline so that the Thursday class could be used productively for refining ideas and gathering feedback.

I worked on the implementation plan and created the outline for the Work Breakdown Structure. I designed an early version of the diagram, but the text became too small to read once it was converted into an image. Later, Manzil developed a version of it on Miro, which followed the same structure but was clearer and easier to share through a collaborative link. I also prepared the high-level Gantt chart after exploring different methods for creating one and adjusting our plan when we encountered technical challenges.

For the contingency plan, I collaborated with Aman to include his points about time and coordination constraints, then added my own suggestions covering technical and scheduling risks. I also contributed to the communication plan using ideas from my previous research on Atlassian’s communication channels, which helped shape how our team shared updates and managed files.

Throughout the week, I conducted detailed research on the technologies and frameworks relevant to our project, including Google Maps SDK, ArcGIS Mapping Services, Open Charge Map API, and Firebase. This research supported both the technology and planning sections of the document.

Overall, my main contribution this week was coordinating the document’s structure, managing the workflow, and combining research, planning, and communication elements to bring the report together as a cohesive submission.

Comments

Post a Comment

Popular posts from this blog

Week 3 Blog: Individual Contributions

By
 This week I suggested that we build a web-based application, since it would be easier to present and maintain . I also shared my screen to walk my team through serveral of my past project s, includes a Movie Review Web App , an Advanced Web Project , a Shooter Game and a Task/Calender App . These demonstrations highlight my technical ability acrosss both web and game development and based on this the team suggrested that I would be the most suitable choice to take on the role of main developer for the project. Beyond my project showcases, I also supported our collaboration setup by creating a Discord server so the team could share updates and stay connected outside formal meetings.
Read more

Week 3 Blog: Individual Contributions

By
Tausif Rahman This week I presented the  Audit App  concept with its two parts:  Order Audit (OrderAuditPro)  and  Walkthrough Auditor . I later uploaded documentation and demonstration files of an Android version of the Order Audit module, which helped the team understand the concept more clearly. In addition, I encouraged the team to think about their  past subject projects  by asking what they had worked on in Android, iOS, cross-platform, and project management courses, to see if those experiences could be adapted into our current project. Alongside that, I shared several of my own past coursework projects, such as  ScholarSwap  (resource and book exchange platform),  SurvivAway  (a budgeting and life-flow helper), and  FocusFlow  (a study planner with ADHD-focused features). I also raised the issue of  legal risks  in some ideas, such as consumer liability in a Parking App or data security concerns in a Pass...
Read more

Week 5 Blog: Individual Contributions

By
  participated in the voting process and initially leaned toward the Audit App, but after deeper discussions, I found the Customer Service Checker and Vehicle Manager ideas more scalable and innovative. I located an academic paper titled E-Charge, which described an EV-charging-station planning system using open data and efficiency modelling. I shared the paper with the group and led a discussion on how its methods could guide our approach—particularly its use of driver-collected data, efficiency mapping, and route-planning optimisation. I also helped analyse how to simplify our version for Trimester 1, keeping it practical while leaving room for AI integration later. Additionally, I began finding and reviewing more EV-planning research papers to contribute to our shared knowledge base.
Read more