If a vendor that you’re already familiar with unveils a new software tool, do you adopt it immediately or wait to see if any bugs or problems arise?

EngineeringVendor Management
3.3k viewscircle icon5 Comments
Sort by:
Director of Technology Strategy in Services (non-Government)2 years ago

Only if it solves a problem I have already identified. 

Lightbulb on1 circle icon1 Reply
no title2 years ago

+1

Program Manager II in Healthcare and Biotech2 years ago

I would wait to assess if any bugs or issues arise before considering adoption.

Lightbulb on1
Co-Founder in Services (non-Government)2 years ago

Do you mean Featrue or bard new tool?  From my point of view it will depend, what kind of access the tool has, what happened to data and etc, , so basically it depends :) 

CEO in Healthcare and Biotech2 years ago

We always do a check in a sandbox environment

Content you might like

Is Vendor Management part of Procurement in your organization?  

Yes, it's integrated together55%

No, VMO is separated41%

Other (comment below)2%

View Results

What factors help your team decide that it's time to stop software testing for a release? Choose the top 3.

% of tests executed/test coverage30%

% of requirements covered by testing/code coverage43%

% of total tests passed45%

% of critical tests passed38%

% of critical business flows passed29%

Project deadline is reached21%

Project budget is reached14%

Minimum acceptable defect rate is achieved12%

Go/No-Go meeting11%

Other1%

View Results

How do you get your team excited and motivated to take on a massive new project? Aside from sharing details, goals and steps, do you have a strategy for helping your team feel truly engaged?

What’s the best way to deal with skepticism from your software staff about an upcoming major change in their development process?

Do you find it hard to say no to unreasonable requests for your software team? How do you frame your “no” so it doesn’t cause problems with the team making requests?

Read More Comments