In our previous article we started talking about the processes of our work. We covered many steps, including log tracking and infrastructure building. The second part of the topic will give you more information about further steps of DashBouquet work.
As we always say, we use limited amount of tools, but we aim to make the most out of them. So for each project we highlight key areas of expertise and always organize 20-minute seminars on situational training during the development process.
This approach has two visible advantages. First: we get extra training for the areas that require most of our attention. Second: we constantly learn and make sure to apply this knowledge in other projects with similar tasks. We believe that such narrow focus helps us in achieving results.
We usually do planning for two weeks ahead. This helps us in managing our time and sources efficiently and timely implementing any changes needed. At the end of each sprint we do a demo, during which we present the results of our work and current project status, update the client about budget, present him a visual changelog and together plan the next spring.
What matters the most to us is clear and transparent communication – “no walls” between DB team and the client. We organize Skype meetings, use Slack and other messengers. We don’t want our clients to miss any single piece of information.
At the end of each project we get together with the team and do a retrospective. Post-project analysis is as important, as pre-project analysis, because we can see everything: where we went wrong and what we did right.
Our project team involves following people:
- Tech lead: responsible for architecture design, code review, training
- Developers: responsible for smooth-running code
- QA: ensures we deliver constant quality
- PM: the project manager and project superhero
- Accountant: manages the budget
As you see, nothing over-complicated in other processes. What we always try to do is:
< Focus on what matters >
< Analyze everything >
< Keep communication with the client going >
In our next articles, we will be looking at our projects in more detail, covering specific tools and work methods that we use.
Responsibility between the Client and the Development Company
For an outsourced software development company, communication and workflow organization are the keys to a successful and effective collaboration. In addition to communication and organization, there is also an issue of shared responsibility and trust.
The Always Important Human Factors in Development
The science of human factors makes a compelling case for becoming integral in the development of almost any product or service. It moves the conversation from what you envisage will happen in theory to what will actually happen in practice due to human traits, quirks, limitations and general characteristics.
Soft Skills for Developers: Why Do they Matter and Which Ones are the most Important?
Technical and soft skills for developers go together like peanut butter and jelly. Though the employer will first be looking at the tech background and the experience with specific tools, soft skills determine whether the person will stay in the team for a long time.
01 / 04