2011 Defining Lean Software Developers 
Inloox
JULY 1, 2021
What usually started in software development can now be extended to the entire company and thus, change the way people collaborate. SAFe picks up many already familiar elements and concepts from existing methods such as Scrum or Lean Project Management, which makes the transition easier for many companies.
Agilemania
DECEMBER 6, 2021
It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps. Software and IT teams delivering in an agile way alone isn’t enough.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Agilemania
JANUARY 24, 2022
These frameworks also encourage you to use Lean principles to optimize your flow. In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. What is SAFe?
Scrum.org
JANUARY 6, 2022
As of today the top 10 most valuable companies in the world as defined by market capitalization are Apple, Microsoft, Saudi Oil Company, Amazon, Alphabet, Facebook, Tencent Holdings, Tesla, Alibaba, and Berkshire Hathaway. Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different.
Leading Answers
APRIL 22, 2018
“ Software is eating the world ” claimed venture capitalist, Marc Andreessen in his 2011, New York Times article. Software is becoming omnipresent, it is embedded and integral to all industries. Next, the idea of a “project” with a defined endpoint is dissolving too. Role Changes.
Epicflow Blog
MAY 14, 2019
Christine Basson , a Project Director at INEOS, says that you should “never underestimate the power of a well defined business case. Poorly defined business objectives are translated into a poorly defined project, lots of changes, [and an] unstable project platform. Facts and Fallacies of Software Engineering by Robert L.
Herding Cats
MAY 10, 2019
IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Defining Uncertainty in Projects ? 3, March 2002. 255, April 2010. 920, November 2004.
Expert insights. Personalized for you.
100 
Let's personalize your content