Finalize Dev & UI Standards
Every team member contributes a unique set of skills on the project. Within the framework of the project governance model and roles and responsibilities, the team is expected to come together to deliver the project. It is therefore important to have the development team discuss the set of software and systems engineering standards, and agree on how these standards will be selected and tailored.
Documented development standards help ensure that the product you are building are fit for their stated purpose and when these standards are used consistently by all developers on the team, you are assured of good practices, which reduce maintenance costs and total cost of ownership for the application. This is particularly useful for more junior resources. The main goal of conforming to standards is to make the application consistent in the way it was architected and developed, and to make it easier to maintain for future development.
Systems that are developed to standards also make them more credible. Software that is developed to a set of standards can be more cost-effective because it becomes easier to implement and to learn for those who are charged with maintaining it after the initial release is completed.
Development standards cover accessibility, performance and responsive design, coding techniques for error messaging, formatting, graphics, version control processes, and other specific principles which must be consistently applied by all development team members. The project’s technical lead should organize a standards meeting, in partnership with all the relevant technical resources. This meeting is used to discuss, document and communicate the standards to everyone on the development team, to minimize costly rework in later sprints and also to curtail unnecessary waste of development resources to refactor code.
Published May 8, 2018 — Updated January 11, 2019