While working on the project we try to stick with best practices in architecture for development and design that help us to produce better quality code and make the overall process more effective.
- Increase overall efficiency for each team member in person and the whole team in general
- Reduce the number of mistakes and avoid common pitfalls
- Strive to be a better engineer and learn by other people's shared experience
- Always target high code quality bar, constantly polish your dev skills. Slow down to go fast. Value quality and precision over ‘getting things done’
- Work diligently on the one important thing
- Remember we are a distributed team and sharing context via wiki, slack and backlog items is essential
- Make the simple thing work now. Let’s build fewer features today, but ensure they work amazingly and add more features tomorrow
- Avoid adding scope to a backlog item, finish the current thought and add a new backlog item
- Remember to tether to ‘Done’ for a backlog item. Our goal is not to write code, it is to ship incremental customer value. Our job is likely not done until our code is in production adding that value.
- We all own our code and each one of us has an obligation to make all parts of the system great
- Keeping backlog item details up to date is how you communicate the state of things with the rest of your team. Discipline around updating status, assignment, comments etc is essential
- Treat project/component as your own product: constantly see how to improve it (from developer's perspective and public functionality)
- Report product issues found not related to your task