Most companies seem to fall into these three categories in regards to software development:
As we are trying to be the perfect mix between Employees, Consultants and Outsourcing, we have the following three key benefits described below. In addition, we also try to challenge your requirements and needs, to make sure you get critical feedback on projects and tasks.
After starting a project, you get access to the Jarboo Workspace. The project manager will assemble the team you need, depending on technology, project size and requirements. The team is updated as we go along, depending on your needs.
In the Jarboo Workspace you can communicate with a project manager, create tasks and see the status of existing tasks. If you need something done? Create a project or task, and we will get to it.
We start when an estimate for a task has been accepted. On all tasks, there are five development phases which are covered below.
For complex tasks, there are often 3-5 different people in this process (or more, if it's a bigger project). For simpler tasks it would often be 2 people, to make sure things go smoothly and quickly.
The project manager is responsible for clearing all details about a given task. This is done by breaking down the task into subtasks and understanding the full flow and scope. Often mockups are used in this stage.
For most tasks, the project manager makes a simple test matrix that describes how the test will be conducted when it's done.
The architect will break the task into programmable subtasks of maximum 5 hours, and specify exactly how the task should be implemented.
The architect's role is to consider and make sure the implementation makes sense according to the overall picture.
The developer will make sure things get coded correctly. He will implement as per the architecture descriptions.
The preferred way of working is by having pull requests, meaning the code will be reviewed by someone else than the developer himself, to make sure code quality is at a high standard.
The code reviewer verifies two things. First that the developer did the implementation correctly as the architect described, and second that the code in general has a high quality.
The tester verifies two things. First, that the test the project manager originally described works and makes sense, and second, that the solution in general makes sense.