2006 Risk Software Engineering 
LiquidPlanner
JUNE 1, 2016
In 2006 I left a great gig at Expedia to start LiquidPlanner with a fellow Expedia colleague, Charles Seybold. So, if you’re itching for a new role in which you will directly impact the direction of our growing software company, this could be the gig for you. LiquidPlanner is the only predictive scheduling engine on the market.
Herding Cats
MARCH 11, 2018
If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
DECEMBER 16, 2017
Software Sizing, Estimation, and Risk Management: When Performance is Measured Performance Improves , Daniel Galaorath and Michael Evans , Auerbach, 2006. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.
Herding Cats
OCTOBER 5, 2018
A Quick Estimation Approach to Software Cost Estimation," Leckraj Nagowah, Hajrah BibiBenazir, and Bachun, African Conference on Software Engineering and Applied Computing , . "A A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10
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.
Herding Cats
AUGUST 1, 2018
One chapter on the Principles of Risk Management and the second chapter on the Practices of Risk Management. Since reducible and irreducible uncertainties create risk, those uncertainties need to be reduced as the project proceeds for the probability of project success to increase. 37–48, 2007. So here's the outcome.
Herding Cats
DECEMBER 3, 2017
The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. IT Risk Management.
Expert insights. Personalized for you.
74 
Let's personalize your content