#All #Confluence #Jira #Bitbucket #Case Study #Learning Management #Collaboration #Project management #Task Management #Document management #Reporting #Analytics #Integration #monday #How To #AI #News #Confluence Tutorial

Introducing New Feature: Graphs for Teams in Awesome Graphs

December 3, 2019

#News#Bitbucket#Reporting#Analytics

7 min

There is no doubt that effective working and communication processes in a team greatly influence the overall success of a product or company. Atlassian products like Bitbucket, Jira, and Confluence aim to improve collaboration and bring distributed colleagues together.

Awesome Graphs for Bitbucket app is our contribution to the teamwork of more than 2,000 companies, as its primary goal is to help identify the bottlenecks in the development workflow and increase the speed. We are eager to make the processes transparent for both developers and managers and, thereby, improve the communication and narrow the gap between them.

We’ve discovered that lots of our clients use similar workflows: they have multiple teams working on the same project or repository. Therefore, tracking the productivity of a particular group that a project or delivery manager, or team lead manages can be tricky as the app showed graphs for all the activity across a project or repository that included the statistics about all the teams together. That’s why we decided to implement a feature that can make their lives easier: graphs for teams.

View the statistics for your team

Teams feature is designed to visualize the statistics about your team performance if there’s a lot of people working on a project or repository. It excludes the contributions of the members of other teams and helps get rid of noisy data.

Configure your teams in the settings and choose it in the All contributors drop-down menu on the Graphs page and analyze how much commits, pull requests, and lines of code a team produces apart from others.

Compare the activity of different teams

If you manage multiple teams working on the same project or repository, you may find it useful to separate their statistics from each other. For example, compare their impact in a codebase of your repository using the Code Frequency graph. That’s what you can easily do with our new feature!

Let’s say you manage two teams: back-end and front-end developers. Open a graph for each team in different tabs and compare their performance.

From the screenshot below, you may identify that your back-end team is continuously deleting the lines of code. They are probably involved in some bug fixing or refactoring activities or implement changes in the API.

Meanwhile, the front-end team has to rewrite some pieces of code to adjust the changes in the backend.

Exclude automated users from the statistics

If you use automation in your repositories, the graphs may show the information that is not related to the activity of your team. Lots of commits and lines of code added by CI/CD users and automated scripts may complicate the performance analysis since it’s not obvious which contributions are made by real people and which of them are not.

Use teams feature to solve this problem by creating a team with all the people you need except for the automated users.

Teams management

A team can be made on the global, project, and repository level by the user with administrative permissions on this level. A team can include whole Bitbucket groups or individual users.

It’s possible to create a global team in the Teams tab in the Administration page and view graphs for it in all projects and repositories.

There’s no need to disturb your Sys Admins from their work to create a team. If you’re a project or repository admin, you may do it in the Teams tab in the settings. In this case, your teams’ graphs will be available only in your repository or project and higher.

Improve your teams’ activity tracking

At the moment, graphs for teams are available only for the Graphs page, but we’ll add this feature to the People page and Reports soon in the next releases.

Try a new version of Awesome Graphs for Bitbucket to get even more useful insights on your team productivity and compare the activities of different teams!

We are delighted to implement the team feature that our customers were asking for, and we hope to make their working process a bit easier and better! So, we appreciate any feedback on the app and suggestions that could help you get the most benefit from Awesome Graphs. If you have any, please, feel free to write to us here as we’re looking forward to learning about your needs!

How to Perform Code Review and Track Team Activity in Bitbucket

August 8, 2019

#Case Study#How To#Bitbucket

6 min

Resolution Time Distribution Reports have helped a lot during the development of a high priority module to increase the reviewers, review frequency and also track team activity in Bitbucket.

Eduard Pal, Innoface

Innoface GmbH, one of our customers, is one of the leading providers of interfaces between PDM and ERP systems worldwide. Its applications help ensure a direct and reliable flow of information between engineering and logistics. They also offer additional products and services in order to facilitate seamless integration of the involved systems.

Innoface product development team uses Awesome Graphs for Bitbucket mostly for making data-driven management decisions. They find it very useful to:

track the activity of each developer and a team in general;
check if code review goes according to the plans;
predict time to resolve pull requests.

Let’s see how Innoface benefits from using Awesome Graphs for Bitbucket.

Tracking team activity in Bitbucket

Activity graph helps Innoface have a high-level overview of the total number of commits and contributors in a specific period, for example, a week. It also provides an opportunity to track the number of open pull requests from all the contributors and the repositories.

Using this graph, the manager can assess the activeness of a contributor. This gives the manager an idea of whether an employee is following the company’s development policy or not as well.

Based on the number of open pull requests, the manager in Innoface can actually plan time to review the code and merge them. This graph also gives an opportunity to process the pull requests from the contributors that are working on the high-priority projects.

Analyzing code review practices

Innoface management finds Resolution Time Report very helpful when it comes to tracking the frequency of processing the pull requests.

The manager uses this report in order to see the frequency with which the reviewers are processing the pull requests. Based on the data that this report provides, it’s easier to make a reasonable decision and to assign either more reviewers or increase the frequency of the reviewers, especially for the high-priority projects.

Predicting pull requests resolution time

Resolution Time Distribution report helps Innoface estimate resolution time for future pull requests to make more accurate release dates planning.

The manager of a product team uses this report in addition to the Resolution Time Report in order to estimate the resolution time for future pull requests.

Conclusion

Awesome Graphs greatly enriches the Bitbucket user experience for Innoface. With its help, it becomes much easier to make decisions based on data and keep an eye on how efficient their development practices are.

Read more case studies to see how our customers benefit from using Awesome Graphs for Bitbucket in their work:

Start a free trial of Awesome Graphs