Remove 2011 Remove Innovation Remove Reference Remove Software Developers
article thumbnail

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

Scrum.org

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. References. SCRUM and productivity in software projects: a systematic literature review.

Agile 198
article thumbnail

ITIL 4 Managing Professional Transition Module Training: Career paths after ITIL Certification

Techno-PM

Another benefit is that one of the main goals of ITIL 4 is innovation, which means if you're looking to make changes within your company's operations. The British Standards Institution has accredited them to provide certification for ITIL® professionals based on their latest release, ITIL 2011.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The Complete Guide to Scaling Agile and SAFe for Business Agility

Agilemania

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. .

Agile 98
article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Now To Risk Management.

article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. This corresponds with research on autonomous teams, as well as principles of Agile software development. References. The need for fluid teams. 2007, August).

article thumbnail

Software Estimating Resources

Herding Cats

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

article thumbnail

Estimating is a Learned Skill

Herding Cats

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.