2011 Influencer SCRUM Software Engineering 
Scrum.org
OCTOBER 19, 2022
And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.
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. What contexts are Scrum suited to, and which not? What if you end up applying a methodology like Scrum to a context where it isn’t suited, and people leave the company as a result?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
NOVEMBER 7, 2016
And the same process is applied to the Scrum development processes on those projects. . 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. 5 Oct 1990, Page 21.
Herding Cats
MAY 7, 2019
“Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 9, Issue 3, No.
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. 5, September/October 2011. Software Engineering Institute, January 1996.
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. 5, September/October 2011. Software Engineering Institute, January 1996.
Epicflow Blog
MAY 14, 2019
Varun Maheshwari , a Scrum Master at Telstra, says to “avoid project based thinking and start product thinking, have tight & fast feedback loops, make teams really autonomous, let team members talk to real customers so that they can understand domain & customer needs better, etc. Develop Your Leadership Skills.
Expert insights. Personalized for you.
197 
Let's personalize your content