2011 Software Development Software Engineering 
Scrum.org
FEBRUARY 4, 2022
There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011). That is great!
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. SCRUM and productivity in software projects: a systematic literature review. C., & da Silva, F.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
DECEMBER 16, 2017
The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.
Herding Cats
MARCH 11, 2018
If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.
Herding Cats
MARCH 11, 2017
“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391.
Herding Cats
OCTOBER 5, 2018
The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10
Herding Cats
OCTOBER 24, 2018
But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What Are Problem Causes of Software Projects? All for the want of a nail.
Expert insights. Personalized for you.
218 
Let's personalize your content