Team: 3 Developers (part-time)
For this next sprint, we had only three developers supporting the project as several of our other free-time/part-time developers found full-time jobs and transitioned off.
Due to the lack of developer support, our team made an important decision to transition the remaining pages we still needed to build to use Material UI library components. This would reduce the number of components our developers need to build, and allow us to launch closer to our target date.
In this decision, our designers quickly converted their designs to leverage Material UI components so that our developer knew what to build.
- Page | Collaborator Dashboard
- Page | Collaborator Activities
- Page | Collaborator Manage Projects
- Page | Collaborator Manage Tasks
- Page | Collaborator Settings
- Back-end Set-Up + Dummy Data
- Leveraging a pre-built library, such as Material UI, is helpful to speed up development. The downside is that the designs are not as flexible so it was difficult to make the components match our design system. This is fine as we can work to adjust designs after launching and testing with users.
- We tried leveraging pre-built Material UI page templates, but unfortunately, was not able to make it work with our codebase. Therefore, we only leveraged Material UI base components.
Improvements for Next Sprint:
- Communicate and respond to blockers ASAP.
- Quicker PR Reviews.
- Find more developers to support.
- Leverage similar material UI components across remaining pages to reduce additional work for developers.
With our seventh sprint complete, we move onto our eighth sprint!