Remove 2002 Remove Cadence Remove Risk Remove Underperforming Technical Team
article thumbnail

Questioning Agile Dogma

Leading Agile

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. Stable Team. Dedicated Team. Team Spaces.

Agile 115
article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. Management Processes (#MP).

article thumbnail

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Try installing a typical business application on a pristine development environment.