Scrum.org

OCTOBER 19, 2022

Is it really that important that they are autonomous, able to release frequently, interact closely with stakeholders and spend all that time on continuous improvement? 2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So However, the sheer effort involved is so gargantuan that this is close to impossible.

Agile 197

Agile 2010 2013 2008 197

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. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Accuracy - how close is the estimate to the actual value? 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.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 4, 2019

It just closed the loop faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Engineering Risk Management: Finding your Path Through the Jungle, Version 1.0 , Dale Karolak, IEEE Computer Society, 1998.

Risk Management 43

Risk Management Risk 2003 2011 43

Leading Agile

JUNE 18, 2018

People who specialize in testing software will need technical skills more-or-less on par with competent software engineers. In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Open/Closed. Authoritative.

Software Review 101

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 101

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Two closely related conceptual errors appear to be quite common. First, there’s a tool-centric mentality about software-related work. The company wanted to automate their dispatching process.

Software Review 78

Software Review Software Technical Review Development Team Review 78