Scrum.org
OCTOBER 19, 2022
2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. SCRUM and productivity in software projects: a systematic literature review.
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 11, 2019
Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. 3, March 2002.
Herding Cats
MARCH 11, 2017
So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date. Eggstaff, Thomas A.
Epicflow Blog
MAY 14, 2019
Over 200 PM experts from ExxonMobil, INEOS, DXC Technology, and other companies have shared their experience and proved that it’s a super hot topic. Business drivers have to be translated into project drivers by a strong technical team, not management. Facts and Fallacies of Software Engineering by Robert L.
Scrum.org
FEBRUARY 3, 2020
Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002). Limitations of attention. Limitations of thinking.
Leading Agile
JUNE 18, 2018
Self-organize technical teams on a peer model rather than the Chief Programmer model , to help ensure common understanding and knowledge across the team and to increase the team’s bus number. The level of technical expertise required to use this kind of automation far exceeds that necessary for automating conventional functional checks.
Expert insights. Personalized for you.
197 
Let's personalize your content