Can you justify what you spend on software? On DevOps activities? Like actually put a number on it, not just explain that it’s needed to solve the digital challenges of the business?
SHOW: 646
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"
SHOW SPONSORS:
- Granulate, an Intel company - Autonomous, continuous, workload optimization
- gMaestro from Granulate - Kubernetes cost optimization, made easy
- Datadog Monitoring: Modern Monitoring and Analytics
- Start monitoring your infrastructure, applications, logs and security in one place with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.
- Streamline on-call, collaboration, incident management, and automation with a free 30-day trial of Lightstep Incident Response, built on ServiceNow. Listeners of The Cloudcast will also receive a free Lightstep Incident Response T-shirt after firing an alert or incident.
- Pay for the services you use, not the number of people on your team with Lightstep Incident Response. Try free for 30 days. Fire an alert or incident today and receive a free Lightstep Incident Response t-shirt.
SHOW NOTES:
HOW MUCH DOES IT COST TO CREATE AND RUN SOFTWARE?
How much does a better customer experience cost? How valuable is it to add new partners? Some questions are easy to measure, while others are not. So how do you measure them?
DOES YOUR PROJECT CLEAR THE HURDLE RATE?
- Who decides if a project is important? Is viable?
- How do you measure cost-savings projects vs. business expansion projects?
- Does the CFO decide, or the CMO, or the CRO? Who resolves conflicts?
- Are you prepared to have projects rejected due to missing the hurdle rate?
FEEDBACK?
FEEDBACK?