2005 Influencer Software Engineering 
Scrum.org
MARCH 10, 2025
Try to imagine 1995 through ~2005. They were likely to have had 10 to 20 years of software engineering experience. What did they bring to the role of Scrum Master? It was common they had a well-established career. They had been a manager of teams for many years. They were likely to have founded a company of their own.
Scrum.org
FEBRUARY 3, 2020
Why our brain is not built for software engineering. Although our brain is a marvel of evolution, it has not evolved to excel at the kind of knowledge work (Davenport, 2005) that we actually do most of the time. 2005) Thinking for a living. Below are some of the limitations of our brains that we have to consider.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
FEBRUARY 9, 2019
1] "Systems Engineering Strategies for Uncertainty and Complexity," MITRE Corporation, Systems Engineering Guide. [2] 2] "A Guide to Deal with Uncertainties in Software Project Management," International Journal of Computer Science & Information Technology (IJCSIT), Vol. This solution is called Software Engineering.
Herding Cats
NOVEMBER 7, 2016
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 ‒ Steve McConnell. The Future of Systems-and Software Development. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.
Herding Cats
MAY 10, 2019
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. Elsevier, 2005.
Herding Cats
MAY 7, 2019
Flint, School of Management, Working Paper Series, September 2005.”. Eva Regnier, DRMI Newsletter, Defense Resources Management Institute, Naval Postgraduate School, Issue 12, April 8, 2005. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. Estimating Probable System Cost,” Stephen A.
Herding Cats
MAY 11, 2019
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. Elsevier, 2005.
Expert insights. Personalized for you.
181 
Let's personalize your content