2011 Innovation Software Development Sustainability 
Agilemania
DECEMBER 6, 2021
It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. Software and IT teams delivering in an agile way alone isn’t enough. It’s when the entire organization uses Lean and agile practices to continually deliver innovative business solutions faster than the competition. Take an Economic View.
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. These capabilities support each other and create opportunities for sustained leadership in the marketplace and services. So agility in itself is nothing new for many companies.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Guerrilla Project Management
FEBRUARY 2, 2011
A conversation with Rich Sheridan, CEO of Menlo Innovations, on how agile methods enable his team to build a sustainable and humane work pace while still meeting the needs of his business. Brought to you by: Project Management Telesummit: March 8-10, 2011 – Don’t miss hearing Rich speak at the Telesummit.
Scrum.org
OCTOBER 19, 2022
They found that the ability of teams to develop a shared sense of value contributed significantly and strongly to project success. Hoda, Stuart & Marshall (2011) interviewed 30 Agile practitioners over a period of 3 years. Ultimately, the role of (top) management is to keep their business healthy and economically sustainable.
Agilemania
JANUARY 24, 2022
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. Intel: Intel was reeling under pressure to constantly innovate while controlling costs and maintaining quality. .
Herding Cats
NOVEMBER 12, 2016
Quest for control (in manufacturing sense) makes innovation harder [2]. Innovation causes variability. Organizational culture largely determines if teams and individuals embrace and sustain collective responsibility. Pink, Drive: The surprising truth about what motivates us (2011). . [2] Non-creative work is easier.
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. Software Engineering Institute, January 1996. 3, March 2002. 255, April 2010. 920, November 2004.
Expert insights. Personalized for you.
98 
Let's personalize your content