Code review Agile way


  • For sustainability, the team really should own and evolve their standards instead of them being handed a bible.
  • The coding standards can and should change over time.
  • The key is clarity, testability, extensibility and maintainability of the code itself. 
  • It is also important to establish from the beginning that the code base is shared by the whole team. No part of the code should be understood and maintained by only one team member. 
  • Pair programming is the best way to get consistent adherence to standards.
  • The key is the discipline of unit testing and refactoring

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more