In Valven Atlas, we approach software development analytics in a similar way that we do in real world.
In most companies, the preferred approach is usually to group the units of work into different projects.
Each project has various architecture, design and technology in its nature. Therefore, developer behaviors can change according to project features because some projects can contain processes and technologies that your team is familiar with while another project may require a completely different set of skills in terms of technologies or innovative approaches.
That's why, unlike other development productivity tools, we organize your repositories and reports in projects. In this way, the performance and patterns of your teams can be analyzed for separate projects.
When you are first-time user in Valven Atlas, it's mandatory to create a project to start your journey. You will be redirected to Step 3 of Add Project flow.
Step 1: Click Projects in sidebar
Step 2: Click Add Project in top-right side of page
Step 3: Enter project's name and a description (optional)
- If you have not connected any of your Git accounts yet, you will be redirected to Connected Applications page. For details on how to integrate with other applications, please see here.
- If you have at least 1 Git account connected, you will be redirected to Add Repositories.
Step 5: Select any of your Git and issue repositories that are related with the project, and click Save Repositories. You are allowed to select more than 1 Git & issue repositories in each project.
Step 6: You will be redirected to the Project detail. Valven Atlas will shortly start analyzing your metadata to provide insights into your team's development behavior combining the Git analysis with your issue management system analysis. We normally process the data in under 10 minutes, but for the newly added projects it can take up to 1 hour. You just need to wait until the data is processed.