Project Team Management Guidelines

11. WeekDevelopment Cycle

Follow

• a 1-week sprint cycle to ensure consistent delivery and review a features. 
  • DeveloperDay 1-4: Developers must create a PRpull request for thetheir assigned task inwithin 4four days (It
    should be up to the
    • Tech Leads toare breakresponsible for breaking down tasks into issues that can be donecompleted duringwithin athe week)sprint
  • Day 1 Day5: Review Periodperiod for Tech Leads and Peer Reviewers
    
  • 1-2 Day to6-7: Developers address review comments and merge the pull request
  • The PMs should be in charge of monitoring the merging of pull requests based on feature prioritizationPR
    

Note:

PMs are responsible for monitoring PR progress and ensuring merges are prioritized according to feature requirements.

2. Peer Review Policy

Peer reviews are an essential part of maintaining code quality and knowledge of the codebase across the team.

• PairingEach updeveloper eachis of devpaired with another dev.developer Theyfor shouldmutual bereview mutuallyof each other pull requestsPRs
• ThePairings are assigned by the Tech Lead should be in charge of assigning the peers
  
• The Tech Lead should review every pull request regardlessto ensure technical quality

3. Final Notes

By following these guidelines, the team leaders ensure that development cycles remain efficient and collaboration is encouraged. Clear ownership between Developers, Tech Leads, and PMs allows for consistent delivery and reduced bottlenecks.