2010 Software Software Developers Strategy 
Scrum.org
AUGUST 1, 2022
It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). These are fine strategies. In Achieving Quality in Software (pp.
Scrum.org
OCTOBER 19, 2022
2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ).
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Gunther Verheyen
APRIL 24, 2020
Having worked with Scrum since 2003, I am fascinated by its ever-expanding use, which is not limited to software and (new) product development. Jeff Sutherland and Ken Schwaber moved the development of Scrum forward in the early 1990s. Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.”
Herding Cats
MARCH 17, 2019
Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. How to Develop Credible Cost & Schedule Estimate.
Project Pulse Journal
MARCH 25, 2024
Their tasks revolve around using customer feedback for product improvement, gathering feedback, creating product roadmaps and pricing strategies, solving planning roadblocks, and keeping abreast of market trends and competitor activities. Continuous Improvement It ensures sustained competitiveness and relevance.
Scrum.org
MAY 26, 2020
“ Christiaan : A friend of mine started a software company. He sold solutions, I developed them. Barry : Failed software development projects. Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. Developers, because of the growing crunch-culture.
Herding Cats
MAY 10, 2019
This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 255, April 2010. 24, 2010. “A requires making estimates) ? 3, March 2002.
Expert insights. Personalized for you.
236 
Let's personalize your content