2009 2010 Risk Software 
Scrum.org
AUGUST 1, 2022
It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). In Achieving Quality in Software (pp. R., & Chu, A.
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
Herding Cats
DECEMBER 16, 2017
The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. IT Risk Management.
Herding Cats
MARCH 17, 2019
Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Business, Technical, Systems, Risk, and Project Management. Risk Management.
Herding Cats
OCTOBER 5, 2018
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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.
Herding Cats
MARCH 11, 2017
The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.
Expert insights. Personalized for you.
233 
Let's personalize your content