5 Sprint Overview - mariusb03/WebAndApplication-group-18 GitHub Wiki

image

Sprint 1:

The primary focus of the project planning phase was to establish a robust foundation for the project through comprehensive documentation and strategic groundwork. Key deliverables included:

  1. Group Contract: A formal agreement outlining team roles, responsibilities, communication protocols, and conflict resolution strategies to ensure smooth collaboration.
  2. Use Case Diagram: A detailed representation of the system's functionality, illustrating how users will interact with the system to achieve specific goals.

Establishing the initial technical setup, including selecting tools, frameworks, and technologies, as well as defining the project scope, timeline, and milestones. These components were critical in aligning the team’s efforts, clarifying project objectives, and laying a solid groundwork for successful development.

Sprint 2:

This sprint concentrated on developing the wireframe and Entity-Relationship (ER) diagram for the database, laying a critical foundation for the work ahead. These deliverables were essential in creating the blueprint for both the front-end and back-end development of the project.

  • Wireframe: A visual representation of the user interface, outlining the layout, navigation, and core functionality of the application or website. This blueprint guided the front-end development by providing a clear structure for the user experience and interface design.
  • ER Diagram: A detailed diagram defining the database structure, including entities, relationships, and attributes. This served as the foundation for the back-end development, ensuring an efficient and scalable database design to support the application's data needs.

This sprint was pivotal in aligning the team’s vision, enabling effective planning, and setting the stage for seamless front-end and back-end integration in subsequent phases.

sprint 3:

This sprint focused on initiating the front-end development and ensuring it closely matched the previously designed wireframe. The primary goal was to translate the wireframe’s visual blueprint into a functional user interface, laying the groundwork for an intuitive and visually consistent user experience.

  • Front-End Development: The team began implementing the user interface, including layout, navigation, and interactive elements, using the wireframe as a guide. This involved selecting appropriate front-end technologies (e.g., HTML, CSS, JavaScript, or frameworks like React) to bring the design to life.
  • Wireframe Alignment: Emphasis was placed on ensuring the front-end implementation accurately reflected the wireframe’s structure, design, and functionality. Regular reviews and iterations were conducted to maintain fidelity to the wireframe, addressing any discrepancies to achieve a seamless user experience.

This sprint was crucial in transforming the conceptual design into a tangible interface, setting the stage for further front-end enhancements and integration with the back-end in future sprints.

sprint 4:

This sprint concentrated on multiple key activities: developing the database, engaging in self-study, planning, and creating a new and improved wireframe. These efforts were essential in advancing the project's technical foundation and enhancing the user interface design.

  • Database Creation: The team worked on designing and implementing the database, following the structure outlined in the Entity-Relationship (ER) diagram. This involved setting up tables, defining relationships, and ensuring the database was optimized for scalability and performance to support the back-end functionality.
  • Self-Study: Team members dedicated time to self-directed learning to deepen their understanding of relevant tools, technologies, and best practices. This included studying database management systems, front-end frameworks, or other technologies critical to the project’s success.
  • Planning: The sprint included strategic planning to refine the project timeline, allocate resources, and set milestones for upcoming phases. This ensured alignment across the team and clarity on project objectives.
  • Improved Wireframe: A new and enhanced wireframe was developed, building on the previous version. This updated blueprint refined the user interface’s layout, navigation, and functionality, incorporating feedback and insights to improve the user experience. this also include the wierframe for mobile phones

This sprint was pivotal in strengthening the project’s technical and design foundations, fostering team growth through self-study, and ensuring a clear path forward through effective planning and an optimized wireframe.

Sprint 5:

This sprint focused on refactoring the front-end to align with the updated wireframe and ensuring the interface was scalable for mobile devices. These efforts were critical to enhancing the user experience and ensuring compatibility across different devices.

  • Front-End Refactoring: The team restructured the front-end codebase to match the new wireframe’s design, layout, and functionality. This involved updating HTML, CSS, and JavaScript (or relevant frameworks) to reflect the refined user interface, improving usability and visual consistency.
  • Mobile Scalability: Special attention was given to making the front-end responsive and optimized for mobile devices. This included implementing responsive design techniques, such as flexible layouts, media queries, and mobile-friendly navigation, to ensure a seamless experience on smartphones and tablets.
  • Wireframe Alignment: The refactoring process prioritized fidelity to the new wireframe, incorporating its updated features and design improvements. Regular testing and feedback loops ensured the front-end accurately reflected the wireframe’s vision.

This sprint was essential in modernizing the front-end, enhancing its adaptability for mobile users, and ensuring the interface aligned with the project’s updated design goals.

Due to other priorities, such as personal reasons or other school subjects, most of this work was not completed and was pushed to a later sprint.

Sprint 6:

This sprint was supposed to focus on optimization, but because of the previous sprint, this sprint took on most of the work from the last sprint.

Sprint 7:

This sprint was intended to focus solely on documentation and optimization of the project. However, due to delays from the previous sprint, it became a catch-up phase where most of the outstanding work was completed, including the planned documentation.

  • Documentation: The team prioritized creating and refining critical project documents, such as the group contract, use case diagrams, and technical specifications, to ensure clear communication and alignment for future phases.
  • Optimization: Efforts were made to improve the performance and efficiency of the existing codebase and database, addressing bottlenecks and enhancing scalability where possible.
  • Carryover Work: Due to the backlog from the previous sprint, the team tackled incomplete tasks, including front-end refactoring, database implementation, and alignment with the updated wireframe. This ensured the project remained on track despite earlier delays.

This sprint was critical in addressing overdue tasks, completing essential documentation, and optimizing key components, paving the way for smoother progress in subsequent sprints.