Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. When it is suggested that estimating is hard, of no value, and unnecessary, always ask what principle is used to support that claim? Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Don't hear one?

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

MARCH 17, 2019

Business, Technical, Systems, Risk, and Project Management. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008. Risk Management. Five Easy Pieces: The Essentials of Managing Programmatic Risk , 10th Annual Rocky Mountain Project Management Symposium, Denver Colorado, April 2008.

2003 54

2003 2011 2008 Performance Measurement 54

Susanne Madsen

MAY 23, 2018

​A project is a unique undertaking that’s full of risk and uncertainty, because it has never been done before in that exact way. Just consider the most important techniques we use as project managers: we define scope, analyse requirements, plan and estimate work, add contingency, manage risks, track changes and check the quality.

Construction 87

Construction 2002 2008 Engineering 87

Scrum.org

FEBRUARY 22, 2021

It could handle the tactical or strategic nature of the suggestion, a possible time-frame, or an estimate of the expected return on investment. Do you remember the origins of the financial crisis from 2008? Bonus-relevant KPIs (key performance indicators) are at risk of not being met.

Software Review 194

Software Review Cadence Technical Review SCRUM 194

Planio

MAY 22, 2023

Estimate the work and plan the release dates 6. Release too often, and you risk overwhelming your users. For example, when Airbnb launched in 2008, its product vision might have been: “In 5 years, Airbnb will be the more affordable and enjoyable way to plan a trip.” Consider your organization’s release capability (i.e.,

Planning 78

Planning Agile Software Review Estimate 78

Herding Cats

MARCH 11, 2018

When we hear about software development disasters and then hear that estimates are to blame, and NOT Estimating will somehow reduce or prevent these disasters, think again. Research clearly shows the root causes of most software projects cost and schedule overruns and technical shortfalls comes from poor risk management.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Leading Answers

AUGUST 29, 2020

Eric Ries documented his lean startup methodology in 2008 as a way for organizations to adapt and experiment with new ideas and perform market tests. With all the planning, estimation, risk management, and earned value tracking, there was a fair amount of math and admin involved.

Technical Review 78

Technical Review Energy Infrastructure Software Review 78

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. The risk is created when we have not accounted for this natural variances in our management plan for the project. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Herding Cats

JUNE 25, 2016

There's another rash of Twitter posters supporting the conjecture that decisions can be made about how to spend other people's money without estimating the impact and outcome of that decision. Theory of Decision under Uncertainty, Itzhak Gilboa, July 2008. Managerial Decision Making Under Risk and Uncertainty Ari Riabacke.

2008 44

2008 Estimate Finance Software Developers 44

Planio

JULY 22, 2020

Risk Up Front: Managing Projects in a Complex World. However, while this book covers basics like estimating and planning projects, where it shines is in covering the soft skills of project management. Published date: 2008 (revised edition). Risk Up Front: Managing Projects in a Complex World. Author: Scott Berkun.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

OCTOBER 15, 2017

VanderLeest GLSEC 2008. "A And of course, each of these domains operates in the presence of reducible and irreducible uncertainty requiring Risk Management processes. When managing any project as Risk Managers as Tim Lister suggested, we need to make estimates in the presence of these uncertainties as well.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. 72, 2nd Quarter, 2008, pp. Olagbemiro, Dissertation, Naval Postgraduate School, December 2008. "A IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Related articles.

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Business, Technical, Systems, Risk, and Project Management. But in fact, risk management is part of the other 4 principles as well. Table of Contents (Click the Name to go to Section). Management Processes (#MP).

Technical Review 42

Technical Review Performance Measurement 2003 Underperforming Technical Team 42

PM Times

APRIL 7, 2021

It will discuss why the Core IT Complexity model is a good approach for most IT organizations and why it is important to determine project complexity as an ongoing and integral part of the Change Management and Risk Management process. It can also indicate potential risks to existing projects. Introduction. Kiridena, S. & Sense, A.,

2016 52

2016 2014 PMO Software Review 52

Herding Cats

JANUARY 8, 2018

1] Apollo Root Cause Analysis: Effective Solutions to Everyday Problems Every Time, 3rd Edition, Dean Gano, Atlas Books, 2008. [2] IT Risk Management. Herding Cats: Principles of Cost and Schedule Estimating. Why Guessing is not Estimating and Estimating is not Guessing. Related articles.

2008 34

2008 2011 Manufacturing Estimate 34

Herding Cats

JULY 24, 2017

The paper on the Cone of Uncertainty is used by many in the No Estimates community as an example of why estimates are of little use. In this paper, there is data that does not follow the Cone of Uncertainty, in that the uncertainty of the estimates does not reduce as the project proceeds. Then there is some analysis.

2007 42

2007 2012 2006 2008 42

Herding Cats

SEPTEMBER 25, 2018

Of course, all three of these are operating in the presence of uncertainty and therefore require estimates to be made. Estimates of the aleatory and epistemic uncertainties that create risk to the delivered Value need to be handled. Keeney, Militarty Operations Research , Volume 13, Number 2, 2008, pp.

Artificial Inteligence 34

Artificial Inteligence 2009 2013 2005 34

Herding Cats

DECEMBER 8, 2017

This can be the confidence in the estimate for any variable. The CoU is a build-to paradigm, where measures of the program's performance cumulative to date is used to inform the risk for future performance. This usually results in a project's actual costs far outrunning the optimistic estimates and creating a large overrun.

Performance Measurement 35

Performance Measurement 2017 Technical Review 2008 35

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. Some feel that the cone does not provide any value for the work they do and does not match the reducing uncertainty in their estimates. This letter states.

2007 34

2007 2012 2010 2009 34

Herding Cats

JULY 8, 2018

One of the books used by a vocal No Estimates advocate is Black Swans by Nassim Taleb. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. The No Estimates advocates have a similar set of behaviors.).

2002 34

2002 2008 Technical Review Software Review 34

Herding Cats

SEPTEMBER 19, 2018

Estimation is part of project management. . The most important estimates for the project manager are related to time and cost. . Since it is easier to estimate small tasks, these estimates are often calculated and performed as point estimates, for example, a task will take 3 days. My proposal is don't estimate.

2010 43

2010 Technical Review Estimate Software Review 43

Herding Cats

OCTOBER 20, 2017

Then we have to Estimate what these measures need to be so the third variable of Little's Law can be Calculated. It has been suggested that with Little's Law No Estimates (#NoEstimates) can be applied. So estimates are needed to produce numbers for this demand, rather than measuring the demand. IT Risk Management.

Underperforming Technical Team 34

Underperforming Technical Team 2008 Estimate 2011 34

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

JULY 8, 2018

One of the books used by a vocal No Estimates advocate is Black Swans by Nassim Taleb. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty. The No Estimates advocates have a similar set of behaviors.).

2002 28

2002 2008 Technical Review Software Review 28

Herding Cats

JANUARY 22, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Aleatory and Epistemic uncertainties, which create the risk to the success of the project. This is due to many reasons.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Aleatory and Epistemic uncertainties, which create the risk to the success of the project. This is due to many reasons.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Aleatory and Epistemic uncertainties, which create the risk to the success of the project. This is due to many reasons.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Wrike

MAY 19, 2021

Business model canvas explained “Lengthy business plans often increase the risk of failure,” wrote Alex Osterwalder in his 2008 book “Business Model Generation.” Be clear and precise with the estimated business costs of the planned activities to ensure you reach your profitability goal.

Lean 36

Lean 2008 Innovation Retail 36

Resource Guru

JUNE 23, 2023

Plus, the risk of human error is just far too great. Founded in 2008 by Dustin Moskovitz (yes, that Dustin Moskovitz) and Justin Rosenstein, Asana quickly became a force to be reckoned with in the work management space. Time tracking: Track the time spent on tasks, estimate project timelines, and generate accurate timesheets.

Software Review 52

Software Review Technical Review Software 2021 52

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. When I left for the airport this morning to catch my flight to a customer site I estimated, given the conditions, how much time I need to get to my favorite parking spot at DIA. So when you hear we can't estimate you'll know better.

Estimate 64

Estimate 2005 2006 2013 64

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9, Estimating Probable System Cost,” Stephen A. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

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. requires making estimates) ? Risk Management Papers. “A

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. Risk Management is essential for development and production programs.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

Teamweek

MAY 21, 2020

Are there any constraints or risks? Asana was founded in 2008 by ex-Google and Facebook engineers. Team members can also add a daily estimate in hours for each task. Looking at these granular estimates helps ensure that team members are not overwhelmed or underworked, and projects are adequately staffed. Project planning.

2020 52

2020 Planning Software Review 2011 52