-
Notifications
You must be signed in to change notification settings - Fork 0
Postmortems
- Iteration 1 Summary (Due Sept 29th)
- Iteration 2 Summary (Due Oct 13th)
- Iteration 3 Summary (Due Oct 27th)
- Iteration 4 Summary [Release 1] (Due Nov 10th)
- Iteration 5 Summary (Due Nov 24th)
- Iteration 6 Summary (Due Dec 29th)
- Iteration 7 Summary (Due Jan 12th)
- Iteration 8 Summary [Release 2] (Due Jan 26th)
- Iteration 9 Summary (Due Feb 9th)
- Iteration 10 Summary (Due Feb 23th)
- Iteration 11 Summary (Due Mar 8th)
In this iteration, the team focused on establishing a strong foundation for the project. This involved organizing the repository, documenting initial requirements, and creating a preliminary understanding of the architecture and technology stack. The primary goal was to set the stage for subsequent iterations.
- Created initial project documentation.
- Defined the foundational software architecture and technology stack.
- Outlined the risk management plan.
- Adjusting to new tools and workflows.
- Ensuring all team members were aligned on the architecture and objectives.
- Begin detailed planning and implementation for core components.
- Create UI mockups and gather stakeholder feedback to refine requirements.
In this iteration, the team worked on setting up the foundational elements of the project, including basic infrastructure, initial project documentation, and planning the system architecture. Progress was slightly delayed due to awaiting stakeholder feedback on key aspects of the project.
- Established the initial project structure and documentation.
- Defined, updated, and finalized the system architecture and tech stack proposal.
- Received updated UI requirements from the stakeholder.
- Stakeholder Approval: Waiting for confirmation and details on project requirements slowed down initial progress.
- Slow Pace: Overall progress was slower than anticipated due to coordination and planning challenges.
- Begin creating UI mockups based on updated requirements.
- Improve internal coordination to enable parallel progress while awaiting feedback.
This iteration marked significant advancements in integration efforts, with a focus on setting up core infrastructure and preparing for Release 1. Despite midterm exams affecting team productivity, notable progress was made on containerizing services and developing initial UI components.
- Successfully containerized services, including GeoServer, SonarQube, and PostgreSQL.
- Created UI mockups to guide frontend development.
- Began implementing core UI components.
- Time Constraints: Midterm exams significantly impacted team availability.
- Complexity in Integration: Initial struggles with containerizing services and setting up dependencies.
- Finalize the UI components for Release 1.
- Test and integrate the backend and frontend components.
This iteration focused on finalizing and refining frontend components for Release 1. The team made notable progress in developing key functionalities to ensure a usable prototype.
- Implemented datasets sidebar and metadata display.
- Developed layers sidebar and user navigation options (e.g., map reset, settings, and language selection).
- Ensured basic functionality of the prototype for presentation.
- Frontend Refinement: Iterating on UI components to meet stakeholder expectations.
- Balancing Deliverables: Meeting deadlines while maintaining code quality.
- Begin planning for Release 2, focusing on backend functionality and integration.
- Address bugs and inconsistencies in the UI.
This iteration primarily involved planning for Release 2 and performing minor fixes. The team also focused on learning new technologies to prepare for upcoming challenges.
- Created a detailed plan for Release 2.
- Resolved minor bugs and issues in the codebase.
- Explored and familiarized team members with required technologies.
- Limited Progress: Focused mostly on planning and learning, resulting in minimal tangible output.
- Begin implementing backend functionality and deeper integration with frontend components.
- Test new technologies in a development environment.
Over the holiday period, the team faced challenges in integrating pgstac with the database due to limited documentation. Despite this, minor backend and frontend improvements were made.
- Progressed on backend and frontend development.
- Researched and began integrating pgstac with the system.
- Documentation Issues: Lack of sufficient documentation for pgstac integration caused delays.
- Holiday Availability: Team availability was reduced due to the holiday period.
- Finalize pgstac integration with the database.
- Enhance backend functionality to support frontend requirements.
This iteration saw the successful integration of pgstac with the database, which enabled the team to advance backend development significantly.
- Completed pgstac integration with the database.
- Made substantial progress on backend implementation.
- Addressed outstanding technical debt.
- Technical Complexity: Debugging and troubleshooting pgstac integration.
- Time Constraints: Limited time for backend development after resolving integration issues.
- Begin testing backend components.
- Continue refining the frontend and backend integration.
This iteration focused on delivering a fully functional system for Release 2. The team prioritized backend functionality, integration with the frontend, and testing to ensure a seamless user experience.
- Developed and integrated backend functionalities to support frontend components.
- Added unit tests and end-to-end tests to improve code reliability.
- Successfully connected GeoServer to the database for efficient rendering.
- Backend-Frontend Integration: Ensuring smooth communication between components.
- Testing: Time-consuming but essential to ensure system stability.
- Collect stakeholder feedback on Release 2.
- Plan for future iterations to enhance functionality and address any remaining issues.
This iteration focused on enhancing configuration management, data persistence, and factory reset functionalities.
- Developed data converter for STAC data.
- Added endpoints for filtered datasets.
- Enhanced configuration management, data persistence, and factory reset functionalities.
- Fixed loading bar and data display issues.
- Configuration management and data persistence were critical but challenging to implement effectively.
- Ensuring data consistency across different system components.
- Continue refining the backend and frontend components.
- Collect feedback on the enhancements and plan for further improvements.
Overview: The iteration aimed at improving the user interface and adding new backend functionalities.
- Added endpoints for filtered datasets.
- Implemented fixes for notification prompts and metadata container issues.
- Enhanced data persistence and added mock STAC item data.
- Ensuring seamless integration of new UI components with the backend.
- Addressing bugs and ensuring stability.
- Focus on user feedback for further UI improvements.
- Plan for additional backend functionalities.
Overview: This iteration focused on refining offline functionality and improving deployment stability.
- Introduced offline functionality and added Tile Server as an offline map provider.
- Implemented a toggle for filtering datasets by region.
- Performed maintenance for the build pipeline and resolved port conflicts for the database.
- Added code coverage and enabled user deselection of datasets.
- Implemented full lazy loading for collections.
- Ensuring offline functionality works seamlessly with the existing system.
- Addressing deployment stability issues.
- Continue enhancing offline functionality.
- Collect feedback on the new features and plan for further refinements.