Construction Estimate Influencer Software Engineering 
Scrum.org
FEBRUARY 4, 2022
This post is for anyone who wants to inspire, change or influence others through their efforts as professionals, with emphasis on the latter. Perhaps you’ve read many blog posts about how horrible SAFe is, or how useless estimation is, or what the optimal size of a team is. What is the optimal size of a team?
Herding Cats
MAY 7, 2019
This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
FEBRUARY 3, 2020
Why our brain is not built for software engineering. Knowledge work’ refers to tasks that take place mostly in our minds, like predicting scope, setting up plannings, considering consequences of changes to complex systems, working out test cases and estimating complexity. This will affect all estimates and predictions.
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.
Epicflow Blog
MAY 14, 2019
Read more: Examples of Lessons Learned in Construction Projects. Victorine Ghobeira , a Senior Business Analyst and Project Manager at Dataquest, says that “preventing a lack of resource starts when defining and estimating activities and leads to creating a realistic schedule. Facts and Fallacies of Software Engineering by Robert L.
Herding Cats
MAY 10, 2019
requires making estimates) ? 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. Software Engineering Institute, January 1996.
Herding Cats
MAY 11, 2019
requires making estimates) ? Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.
Expert insights. Personalized for you.
190 
Let's personalize your content