Suggestions
Vitalii Bondarchuk
Helping to develop software, provide technological expertise, and build R&D centers in UA
Vitalii Bondarchuk is a business development professional currently serving as the Head of Revenue for Ukraine at UST. With 11 years of business development experience, including 7 years specifically in IT outsourcing software, Vitalii has established himself as a seasoned professional in the field.1
Professional Background
Vitalii's LinkedIn profile, under the username vbondarchuk, highlights his extensive experience in the IT industry. His role at UST likely involves overseeing revenue generation strategies and business growth initiatives for the company's operations in Ukraine.1
Education
Vitalii's educational background includes studies at Kyiv National Economics University, which has likely contributed to his expertise in business development and revenue management.1
Areas of Expertise
While specific details about Vitalii's current role are limited, his background suggests expertise in:
- Business development
- IT outsourcing
- Revenue management
- Software industry
Industry Insights
Vitalii appears to be active in sharing industry insights on LinkedIn. He has discussed topics such as:
- The differences between outsourcing and outstaffing in the IT industry2
- Collaboration methods with partners and clients2
His engagement on professional platforms indicates that he is likely well-connected within the IT and business development communities in Ukraine and possibly beyond.
Highlights
Our #deliverymetrics and indicators on the projects
According to my recent poll, ✅ 25% measure just a couple delivery metrics, 💹 47% measure many metrics, ⛔️ 27% – don’t measure.
I want to share our approach for evaluating the bottlenecks, the effectiveness of project delivery, and the main critical indicators we are implementing to analyze certain projects.
- For #Delivery measurement There are many approaches to solving this problem. We are using a method based on an Earned Value Management (EVM) approach:
1.1. CPI (Cost Performance Index) gives a sense of project performance from a cost perspective. If CPI > 1 means the Project is under budget. 1.2. SPI (Schedule Performance Index) gives a sense of project performance from a schedule perspective. If SPI < 1 means the Project is behind schedule. 1.3. Work completed by DoD.
- For #Code Analysis We use different #CodeAnalysis tools, that display most of the main quality code indicators. For example, #SonarQube can analyze and generate results for over 25 programming languages, which is higher than most tools on the market.
We check: 2.1. The number of vulnerabilities – these are points in your code that are open to attack. 2.2. Code smells (%) is any characteristic in the source code of a program that possibly indicates a deeper problem. 2.3. Test coverage (%). Code coverage of 70-80% is a reasonable goal for system tests of most projects with the most coverage metrics. Use a higher goal for projects specifically organized for high testability or that have high failure costs. 2.3.1. Manual Test coverage (%). 2.3.3. Automation Test coverage (%).
-
Risks mitigation Risk counting helps to attempt to prepare for the unexpected by minimizing risks and extra costs before they happen.
-
Change requests It’s the situation when we had the Scope at the start of the project and during the sprint product owner or team generated new ideas and added Change requests.
4.1.Amount of Change Requests 4.2. Cumulative Budget Impact (CBI, $) – how will the budget be changed if we accept change requests for delivery. 4.3. Cumulative Timeline Impact (CTI, days) – how will this change the number of days needed if we accept change requests for delivery. 4.4. Proceeding Change Requests (%) – project manager should process all Change Requests, count CBI and CTI for them, and send such information to the client. The client considers this information and provides the solution to what CR we will add to the Scope. The project manager should try to process all CR – 100%. 4.5. Approved with the Client Change Requests (%) – how many Change Requests were approved for adding to the Scope.
More about these metrics and formulas you can read in our blog https://lnkd.in/guEvVyc6
🔈 Do you measure any delivery metrics?
Software delivery metrics give us quantitative ways of measuring our team’s progress and performance.
👋 They help us understand how we deliver and what’s getting in the way. They give us a tool to iterate/improve our delivery while helping us communicate progress to other business stakeholders.
When equipped with relevant data, a manager can also identify project bottlenecks early and effectively; reduce risks and eliminate failures. Multiple studies have shown that the longer it takes to discover a mistake in the code, the more costly it will be to fix it.
Measurement also helps you spot scenarios when “things do not add up” due to unclear or conflicting project requirements.
📊 A study conducted back in 2008, estimated that 68% of surveyed companies were statistically unlikely to have a successful project due to poor project requirements.
More specifically, they were likely to face the following issues:
🔹 Have a budget of 160% more than the original. 🔹 End up with 180% more of the estimated time than expected. 🔹 Deliver less than 70% of the expected functionality.
Sticking this measurement balance is hard, and finding the best individual productivity metrics for software development to track is even more challenging. But not impossible)
