article thumbnail

7 Hidden dangers of project management (Or why even well-planned projects sometimes fail)

Rebel’s Guide to PM

For example, in June 2010 Chrysler merged with Fiat. Merging required some major organizational changes such as introducing new technology, creating a new management team and alternation in business processes and policies. You can’t expect your business to thrive if you are working on a shoestring budget.

Planning 407
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. A strength of such a review is that it allows for the identification of patterns across many studies. 2010, April). Cardozo et. References.

Agile 205
Insiders

Sign Up for our Newsletter

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

article thumbnail

Why Agile Transformations sometimes fail

Scrum.org

Based on my experience working in agile environments since 2010, I did some research and had general observations on the topic. Another observation I have made is a strong focus on delivery, productivity, technology and effectiveness. These contracts consist of the detailed, fixed scope, fixed time and budget.

Agile 253
article thumbnail

Effective Project Communications Management to Avoid Misunderstandings and Delays

Project Pulse Journal

Boosts Project Success Rates: Projects with effective communication strategies are more likely to be completed on time and within budget, meeting all objectives and ensuring successful project execution. Regularly review and update your communication plan to reflect these changes. Newtown Square, PA: Project Management Institute.

article thumbnail

Risk Management Resources

Herding Cats

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

article thumbnail

Agile Unplugged EP04 | Mike Cottmeyer and Matt Van Vleet

Leading Agile

He is helping us build our technology transformation studio. So we first worked together, I guess it was probably back in like late 2009, 2010. So they’re more the management type practices than they are the technical practices. We are doing a LeadingAgile Unplugged and I have a special guest here, Matt Van Vleet.