Delivering Complex Digital Projects

These days, after a website go-live with solutions completely out of the box, I was wondering why we are recognized in the market as the “team that solves” and we succeed in delivering such complex projects, many of them with a shorter term than the expected. I commented on some decisive factors for the success in the execution of these projects.

ACCT has a very large development team and it all starts there. We have Squads within the company that work with a very high number of developers compared to the number of developers that we see in other companies in our market.

Another point in relation to this is that our teams are targeted to more specific issues, such as project architecture, application development, among many other services. In other words, we have a development knowledge base divided by Squads that are working within the project and that benefit this issue of working with something more complex. Once the team is specialized, complexity is merely a matter of going deeper into the problem, of having, according to the technical expertise of the team, a way for the demand to be delivered.

Today, ACCT has a development process where the problem is very well thought out before actually putting its hands together to solve it. There is not much to change the wheel of the car with him walking. First we write the whole functional process, then we think about the technical architecture and only after that we execute the development.

Another factor is that the ruler of the development team is very high. The level of knowledge of our programmers, the stack ie the languages, the frameworks they know, are very advanced things. This makes it much easier to enter a project that has a higher technical barrier.

And last but not least, today ACCT uses agile methodologies to implement projects. With this we value even more the communication, rites and delivery of the project. These rites include daily, planning so that every week we are looking at what is being done and what will be done by the end of next week. Another day-to-day process is the retrospective, where we identify what is going right, what is going wrong and based on that we have an action plan to be able to act on what needs to be improved.

All of this gives us consistency. In addition, when we have a very big problem, we are able to divide it, we think about how it should be done functionally, how it should be developed technically and we will deal with it daily.

Every day we think more about the problem and continue with the deliveries, so this consistency guarantees the final product in a qualitative way.

Comments

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>