Ework Group, a successful firm specializing in connecting consultants, uses CodeScene to effectively navigate the challenges of distributed software development by facilitating alignment, maintaining code quality, tracking key metrics, and optimizing efficiency, ultimately contributing to the success of projects
What are the main challenges on today’s distributed software development teams with respect to delivery efficiency?
In my opinion, as a CIO, it is important to ensure everyone works in the same direction when teams do not meet in person on a weekly basis. When the amount of small talk is heavily reduced, it’s harder to identify early-stage misunderstandings or where additional clarifications might be needed.
People also tend to avoid 'nice-to-know' questions in meetings or asking someone they've never met in person. When these questions aren't addressed during informal interactions, such as in the lunchroom, they tend to remain unanswered. For this reason, we actively work with our teams to understand not only 'what' they should do but also 'why' they should do it. When everyone is aware of the 'why,' we function better as a team, and the need for clarifications is reduced.
How do you and your teams currently use the CodeScene reports?
Depending on our roles in the teams, we use them in different ways. As a CIO, my primary interest lies in obtaining an 'unbiased opinion' of our performance as a development organization and the ability to identify potential risks ahead. I also observe that our teams become more accurate in estimating tasks and maintaining their backlogs when this data is used for reports shared with management – something that facilitates our work planning. In essence, our developers have increased their contribution in the areas of planning and reporting, in addition to coding, after we implemented CodeScene.
Which is the most important metric you are tracking in the CodeScene reports?
We are looking at lead times, throughput and code quality as some examples. We try to follow a group of KPI’s that has impact on each other to make sure that an increased output does not also come with lower code quality or longer lead times for fixing bugs (as one example). By following KPI’s in this way we can ensure that an increased focus on one area does not mean that we lose focus on other areas.
Would it be possible to get this data without a tool like CodeScene?
Is there any specific project you could share metrics about?
Key Insights and Results
Alignment and Risk Identification
Task Estimation and Backlog Management
Increased Developer Contribution
Key Metrics Tracking
Maintaining Code Quality
About Ework Group
