As we’ve already discovered, building software is not as easy as it seems. The process of creating the project includes various complex operations and multiple interactions between many people. Building custom software is complex by its nature, and there’s no wonder that it involves a lot of communication between the team and the customer.
The team for your project will mainly consist of:
- an account manager, who is responsible for business management and customer relations
- a project manager who coordinates the entire project
- a designer
- a frontend developer
- a backend developer
- a quality assurance tester who oversees the code and tests it for bugs
For each project we’re working on, there is a following communication process:
One communication channel. We understand how crucial is time for our customer. Here in Innopolys we believe clear and simple ways of interaction boost productivity and help avoid misunderstandings amid the team and the customer. That’s why we do not support slow and outdated modes of communication, such as email conversations. For your comfort, we are using Slack – team’s chat application, that is easy to use, integrates with project management systems, and gives you complete visibility into all the communication within the project.
Usually, we create a “Microsoft Teams Channel” for transparent and effective communication between the members of your and our team. In this chat room, the users can collaborate, discuss various project details, and ask for advice. The clarity and transparency we gain through such communication channel make the entire working process faster and easier for both parties.
Work on custom software involves many complex operations, a lot of data, and communication. All of these interrelated parts have to be systematized in a proper way and order. It’s hard to imagine maintaining everything needed for building software without decent planning and a careful organization. That’s why we have Jira – a project management software solution designed for developers. With Jira, we keep all the data by the hand and can easily navigate the project. For each project, we create a Jira board, where the development goals, small tasks, and timelines are stated. Also, the tasks are split into “sprints” – short-term development goals, and sprints are divided within the following categories:
- To Do – stories that have been selected for development
- In Progress – stories that are currently in development by a team
- In Review – stories that have been completed by the developer and are waiting to be reviewed by a team
- Ready for Staging – task is ready to be deployed to staging server
- In Test – story is tested by quality assurance team
- Ready for Production – stories that passed review and have been merged and ready to deploy on production server
- Done – story is successfully deployed
- Our goal is for each story to take approximately three hours to complete, so on any given day, each developer should complete 2 – 3 stories.
Internal Project Management
To reach progress, it’s important to assure the proper internal team management. We reach this through daily meetings, where every designer, developer or manager gives the team a report on the work he or she has completed yesterday and presents the tasks for the current day. Not all the tasks can be completed by one person, and completing one goal often involves the cooperation of several developers or designers. In this case, we plan how the task is going to be finished to overcome work blockers as soon as possible.
After the meeting, all the small tasks are written down into our goal tracking system. Then, they are transformed into weekly project goals, then – into monthly goals. All of these small tasks eventually result in the final product. How do you eat an elephant? One bite at a time. How do you build awesome apps? One daily goal at a time.
What You Get in Result
Communication Plan Open