Project Plan from Milestone 2 to Milestone 3 - bounswe/bounswe2025group8 GitHub Wiki

Planning and Development Methodology

To ensure steady progress and adaptability, our team has adopted a strategy of breaking down major milestones into granular, manageable tasks. This approach, which proved highly effective during the first and second milestones, allows us to monitor our development velocity with much greater precision.

We orchestrate this workflow using a robust combination of tools and synchronous communication:

  • Task Management: We utilize GitHub Issues to define unit-level tasks.
  • Progress Tracking: We visualize our sprint status using GitHub Projects.

Collaboration and Communication Improvements

Recently, we have intensified our collaboration through increased face-to-face intra-team meetings. This shift allowed us to create rapid feedback loops, which were essential to keeping pace with our aggressive feature implementation schedule.

We also encountered and resolved architectural discrepancies between the Frontend and Mobile implementations. These challenges were overcome by redistributing responsibilities across team members to ensure feature parity. Furthermore, to streamline Backend development, we established a formal requirement-gathering process where client teams explicitly documented their API needs (see issue #603). In response, the Backend team produced comprehensive technical reports and documentation (e.g., #624, Admin User API Documentation). This structured exchange has significantly reduced ambiguity and improved our cross-team alignment.

Project Management Boards

Below are snapshots from our GitHub Projects board, illustrating how we visualize our roadmap and current sprint status.

1. Roadmap View This high-level view allows us to track the timeline of specific epics and visualize dependencies between tasks for the current milestone.

2. Board View We utilize the board view to track the immediate status of granular tasks (Todo, In Progress, Need Review, Done) during the development sprint.

Future Plans and Roadmap

Our immediate roadmap focuses on fostering a vibrant user community within the platform. Based on recent stakeholder feedback, we have prioritized features that enhance social interaction and moderation.

The table below outlines our rollout schedule for these upcoming enhancements.

Feature / Task Targeted Deadline
Interaction: Commenting on requests Dec 2
Moderation: Community guidelines & Registration integration Dec 2
Moderation: Admin warning functionality Dec 2
Social: User Following system Dec 9
Accessibility: Additional language support Dec 9
Gamification: Functional User Badges Dec 16

Note: Please be aware that this roadmap remains flexible. Plans are subject to change based on development velocity and further feedback from our milestone reviews.

For a detailed view of these targets, please refer to Milestone 2.5 – Hello, Community! and Milestone 3 – Final Delivery.

Milestone Breakdown

Milestone 2.5: Hello, Community!

  • Primary Objective: This milestone serves as the bridge to our final delivery. The core focus is on implementing "social" features and establishing guidelines to cultivate a genuine sense of community among users.
  • Target Date: 9 December
  • Key Deliverables:
    • Social Interactions: Users will be able to comment on help requests and follow other users.
    • Moderation Tools: Implementation of admin warning systems.
    • Onboarding: Drafting community guidelines and integrating them into the registration flow.
    • Localization: Support for an additional language to widen accessibility.

Milestone 3: Final Delivery

  • Primary Objective: This is the culmination of the project. The focus shifts to system stability, completing remaining functional requirements, and finalizing all deployment and presentation materials.
  • Target Date: 16 December
  • Key Deliverables:
    • Feature Completion: Final implementation of all outstanding features, including the Gamification (Badges) system.
    • Deployment: A fully deployed, operational application.
    • Documentation: Comprehensive technical and user documentation, alongside a clean, organized repository.
    • Presentation: Preparation of the final presentation and live system demonstration.