After all the planning time has come to change code. What happens now? Clear evidence of a rookie team is the lack of a Version Control System (VCS) tool and associated processes built around your VCS will provide all the visibility you need to track progress of your software project. Your VCS becomes the source of truth for your project.
Developers when programming use VCS to create a temporary private branch to work from to avoid negatively effecting others while changing code. The developer and rest of the team rely on Software Testing to ensure new and changed code does what is required of it, and the new code MUST NOT break existing functionality. Getting testing right has many profound positive effects on the project, let me explain.
A necessary part of building a culture Making changes to code on one's own in isolation can be problematic for a number of reasons, however, when you get a pair of scrutinizing eyes on your code, all sorts of things are going to come up that you probably had not considered.
I am a developer with modest design skills on a good day, and no formal training in the great arts of Design and User eXperience. However, I have compiled a set of BPs that allow the non designer in me to produce good looking and professional UIs at least I think so, what do you think?.