3. Communication lines aren’t clear
Communication is known as a ‘soft’ skill, but it’s one of the most important skills a person can have. It’s also especially important for development teams working in an agile environment, as we do at 6B.
It’s vital to communicate the vision properly from the outset, but it’s just as important to communicate change requests and feedback throughout all stages of the development process.
Let’s take this idea of change as our example.
It’s impossible to run a project without some sort of change or amendment happening. This may include:
- New tech being released mid-project that would improve how an app or website performs
- Legislation passing that requires a change to a product
- A stakeholder may have a different idea to another stakeholder on how a website or app functions, such as the text on call-to-action buttons, or any images used
- Change in a company’s business direction if people leave
If changes such as these aren’t properly communicated, they aren’t included in the final product. This can then lead to back-and-forths that can add a lot of time to a project build.
Avoiding complexity here is tricky, but having regular touchpoints is the key.
In order to ensure a continuous cycle of feedback and strong communication lines, our teams hold standups and scrums to discuss progress, any issues and the next phases of development.
We also keep shareholders up to date with how development phases are going, sharing releases of a product at various stages for transparency, so that everybody is aware of how a project is moving forward at every stage.