Scrum.org
JULY 14, 2021
Daniel is a Professor at the University of Aalborg and is specialized in empirical software engineering. Daniel Russo to write an academic paper that has been submitted to the academic journal “T ransactions of Software Engineering ”. The theoretical model we constructed from the case studies and existing literature.
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. De Meyer, C. Loch, and M.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. De Meyer, C. Loch, and M.
Epicflow Blog
MAY 14, 2019
Read more: Examples of Lessons Learned in Construction Projects. Facts and Fallacies of Software Engineering by Robert L. Great Planning Disasters by Peter Hall (University of California Press, 1982), recommended by Sean Doull-Connolly , a Senior Process Engineer at TIAA. Perform Risk Management.
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. I think you should read this post, and take it to heart when you write content that is aimed at influencing others. What is the optimal size of a team? Is scaling always a bad idea?
MPUG
MAY 6, 2021
I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. And the last one is, if you can’t influence it, then don’t measure it.
Scrum.org
FEBRUARY 3, 2020
Why our brain is not built for software engineering. According to Wikipedia, feedback control is: Feedback is a process in which information about the past or the present influences the same phenomenon in the present or future. This is where the cybernetic concept of feedback control is useful (Heylighen & Vidal, in press ).
Expert insights. Personalized for you.
241 
Let's personalize your content