summarize this to 50 words

Our group utilized GitHub and Jira extensively to monitor our progress and organize our work according to Agile methodology. These tools proved invaluable in keeping track of tasks, sprints, and overall project development. However, we encountered a significant challenge due to the unavailability of a dedicated backend developer. This gap in our team composition led to delays and difficulties in implementing backend-dependent features, impacting our ability to adhere strictly to our sprint schedules and objectives.

Recommendations for Future Iterations:

Enhanced Team Composition: Ensure that each group has a balanced team composition with members skilled in both frontend and backend development. This balance is crucial for a smooth project flow and to mitigate the risk of bottlenecks in certain development phases. Our experience highlighted the difficulty of progressing effectively without this balance, particularly in tasks that required specialized backend knowledge.

Skill-Based Resource Pool: Develop a resource pool or a list of mentors with various expertise areas that teams can consult when they encounter specific technical challenges. This could compensate for any gaps in team skills and facilitate continuous progress, even when a team lacks a member with a particular skill set.

Agile Methodology Adjustments: Considering our experience and the challenge of having an incomplete team, I recommend adjusting the Agile methodology to include contingencies for such scenarios. This could involve more flexible sprint goals or the incorporation of learning objectives that allow teams to acquire necessary skills on the fly. It's also beneficial to encourage teams to identify potential skill gaps early in the project planning phase and adjust their project scope accordingly.

Compressed Sprints with Clear Milestones: Adopting a structure with three sprints on a more compressed timeframe could incentivize teams to focus and prioritize effectively, reducing the impact of any skill gaps. Clear, achievable milestones within each sprint, coupled with regular check-ins and adjustments, can help ensure that teams remain on track and can adapt to unforeseen challenges.

Regular Feedback Loops: Implementing more frequent feedback sessions with instructors or mentors can help identify and address any issues early. These sessions can provide guidance on navigating challenges like the absence of a backend developer and adjusting project expectations or timelines accordingly.

Our recommendation to enhance team composition directly addresses the challenge we faced due to the lack of a backend developer. By ensuring a balanced team and providing resources to fill skill gaps, future groups can avoid similar obstacles and achieve smoother project progression. Adjustments to the Agile methodology and sprint structure, coupled with regular feedback, can further support teams in adapting to and overcoming project challenges.