Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. In order to make risk-informed decisions, we must estimate the outcomes and the impacts of those outcomes on future activities (cost, schedule, and technical performance of products and services). Related articles.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Wrike

NOVEMBER 7, 2018

66% of organizations use PM software to communicate with clients. [17]. 76% of respondents said they are either “very satisfied” or “satisfied” with their PM software. [17]. Between 2010 and 2020, 15.7 Business services and healthcare are expected to lead job growth between 2010 and 2020. [11]. trillion. [11].

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

nTask

AUGUST 8, 2019

What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs. Due to the changing needs of the software development industry and the failure of the linearity of the Waterfall Model in providing early feedback, many version of the Waterfall Model have emerged.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 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 2009 2010 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.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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. Thesis, George Mason University, 2010.

2007 42

2007 2012 2006 2008 42

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. I came to AHP through a seminar by Dr. James T. A Cardinal number says how many of something there is.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

AUGUST 1, 2018

Reducing Estimation Uncertainty with Continuous Assessment: Tracking the 'Cone of Uncertainty’” Pongtip Aroonvatanaporn, Chatchai Sinthop and Barry Boehm, Center for Systems and Software Engineering University of Southern California , Los Angeles, CA 90089, ASE’10 , September 20–24, 2010, Antwerp, Belgium, 2010.

2012 29

2012 2007 2010 2006 29

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement 2003 Underperforming Technical Team 42

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

DECEMBER 15, 2016

Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Forgetting even more that "agile" is a bottom-up software development solution. Three Increasingly Mature Views of Estimate Making in IT Projects. Chaos Report Myth Busters , . Related articles.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

MARCH 4, 2017

Let's start with a clear and concise description of the problem of successfully managing projects in the presence of uncertainty: Accurate software cost and schedule estimations are essential for non-trivial software projects. As a software project progresses, more information about the project is known.

2010 28

2010 2007 Estimate Aerospace 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). the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

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). the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty.

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). Estimates are needed but are subject to large level of uncertainty. The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

MPUG

JULY 23, 2020

He has extensive experience of both project management, and software development. Previous positions have included VP of development for Welcom, senior director for product management at Deltek, and manager for computerized project management at Worley engineering. We’re very happy to welcome back John Owen today.

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52

MPUG

JULY 23, 2020

He has extensive experience of both project management, and software development. Previous positions have included VP of development for Welcom, senior director for product management at Deltek, and manager for computerized project management at Worley engineering. We’re very happy to welcome back John Owen today.

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects. An estimate of how long it will take. The name of the person responsible.

Software Review 36

Software Review 2005 Technical Review Agile 36

Workzone

APRIL 30, 2020

In 2010 daPulse, created by Wix.com , joined the vast array of project management tools on the market, and in 2017, daPulse went through a transformation to become Monday.com. Designed to come across as colorful and friendly, Monday aims to help you kick your case of the Monday blues through the use of its software. user per month.

2020 38

2020 Software Review Technical Review 2010 38

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software. Am I getting the velocity?

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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

MPUG

OCTOBER 16, 2019

A lot of times I like to have fun, certainly in doing estimating. And that works doubly if you’re working in a software development environment is that, if you’re going to try and make Microsoft Project become your software developers tool, it’s not a right fit. That is great. Add a bucket.

Agile 40

Agile Technical Review Software Review Engineering 40

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. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. 255, April 2010. 24, 2010. “A Estimation of Long?Term reducible and irreducible ? Kwak and J.

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. requires making estimates) ? 255, April 2010.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 4, 2019

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. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. I'm not expecting anyone to read all these books.

Risk Management 43

Risk Management Risk 2003 2011 43

Scrum.org

FEBRUARY 26, 2025

When I started as a Scrum Master back in 2010, I had my set of practices and I evolved. What I am unable to comprehend is the same practices of 2010 becoming anti-patterns for Scrum Teams in 2025. When a Definition of Ready is established, Developers tend to rely more on the checklist and less on communication and collaboration.

SCRUM 135

SCRUM 2010 2025 Technical Review 135