2002 Software Software Engineering Technical Review 
Scrum.org
OCTOBER 19, 2022
2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. SCRUM and productivity in software projects: a systematic literature review.
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 11, 2019
This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.
Herding Cats
MARCH 11, 2017
The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The Development of Progress Plans Using a Performance–Based Expert Judgment Model to Assess Technical Performance and Risk,” Justin W. They cannot be suppressed or removed. 12, 2008.
Epicflow Blog
MAY 14, 2019
Over 200 PM experts from ExxonMobil, INEOS, DXC Technology, and other companies have shared their experience and proved that it’s a super hot topic. Business drivers have to be translated into project drivers by a strong technical team, not management. Facts and Fallacies of Software Engineering by Robert L.
Scrum.org
FEBRUARY 3, 2020
Software development is (generally speaking) very complex. Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002).
Leading Agile
JUNE 18, 2018
Defensive programming consists of learning and using guidelines for software design and coding that tend to minimize the frequency and severity of problems in production. The day came when the software community more-or-less forgot about defensive programming. The Age of the Mainframe. And sleep, too. The Age of the Webapp.
Expert insights. Personalized for you.
197 
Let's personalize your content