Remove CTO Hire Remove Lean Remove Planning Remove Software Development
article thumbnail

Agile Infrastructure Transformation and TBM

Leading Agile

My experience is that in a TBM implementation that is driven by a CTO or even a CIO in a defense mode (“Why are your costs so high?”) A prior CTO gave an excellent explanation of what it looks like to truly understand TCO. ”) is a more than common approach, but falls short of the value and intent of TBM. .

article thumbnail

Scrum for Newbies: How to Use Scrum to Tame Chaos

Wrike

There was precious little time to create the inbound marketing content we were hired for. It’s a method for accomplishing work where teams use principles from the Agile Manifesto made famous by pioneering software development teams back in 2001. Complete refit from wiring to heating to decoration.

SCRUM 43
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Webinar Recap: Project Performance Measurement – Part 1: Overview Of Project Performance Measurements

MPUG

Kyle: If you have any questions during today’s presentation, please send those over at any time using the chat question box on the go to webinar control panel. We do plan to answer your questions throughout the session today. This is part one of the series. Kyle: All right, we’ll go ahead and get started.

article thumbnail

Risk Management Resources

Herding Cats

The Effectiveness of Risk Management: An Analysis of Project Risk Planning Across Industries and Countries,” Ofer Zwikael and Mark Ahn, Risk Analysis , Vol. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 3, March 2002. Raz and E. “A

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. 3, March 2002. 255, April 2010. 920, November 2004.