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. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. And the same process is applied to the Scrum development processes on those projects. . The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

FEBRUARY 9, 2018

Here's an extract from "Chapter 8: Human Behavior and Complexity," Terry Cooke-Davies, in Aspects of Complexity: Managing Projects in a Complex World. This is a cautionary tale for those listening to the #NoEstimates advocates, where anecdotes of bad management are used in an attempt to replace established principles of business management.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

MAY 8, 2016

is not founded on any principle of business management, microeconomics of decision making, or principles of probability and statistics. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. Managing a business profitably is always hard work. It's a fallacy.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

JUNE 7, 2018

This makes no sense for any development project beyond a de minimis project. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. No interconnections.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

AUGUST 27, 2017

The original post, while likely well meaning, coming from direct experience, focuses on ME the developer. And like many posts and tweets about estimating, it's made from this point of view, not the business point view, not from the point of view of those paying the developer. This Value is developed during the Product Planning session.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

MPUG

MAY 6, 2021

He is responsible for the implementation of enterprise project management solutions for Edwards’ clients as well as overseeing the custom application development performed at Edwards around enterprise solutions and Microsoft Project for both desktop and server as well as SharePoint. Fletcher Hearns: Great, thank you Kyle.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. We develop these reference classes using Agile Function Points.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. Rarely are software engineers working on science experiments.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JUNE 7, 2018

This makes no sense for any development project beyond a de minimis project. It can be used to identify appropriate teams, work groups, and a sequence of how the tasks can be arranged. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. No interconnections.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

MPUG

JULY 16, 2021

Welcome to the final part of my three-part series on project requirements management. What is the requirements management baseline? And I think the reason being is that along the way, in this requirements management process, there was not an appropriate traceability and monitoring process set up. Something is going on here.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Uncertainty creates Risk. Risk management requires active reduction of risk. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. 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 notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. 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 notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. 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). This is done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. First, there’s a tool-centric mentality about software-related work. Building software.

Software Review 55

Software Review Software Technical Review Development Team Review 55

MPUG

OCTOBER 15, 2020

Satya is a management professional, speaker, coach and author of six books, including the book I Want To Be An ACP. So, first thing it is coming from PMI, which is Project Management Institute, a body for project management related certification based in the US. All right, we’ll go ahead and begin. A number of tools.

PMI 52

PMI Certification Software Review Technical Review 52