Herding Cats

JULY 29, 2017

Better have a plan to reduce technical and programmatic uncertainty (both of which have aleatory and epistemic behaviours respectively) at a planned rate, for a planned cost, on a planned time. Or plan on being late, over budget, and reduced probability of technical success, before you start. Related articles.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What Resources will be needed to reach Done?

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

JANUARY 23, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

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.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

FEBRUARY 9, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

DECEMBER 8, 2017

I work in a domain where the CoU is baked into the Integrated Program Performance Management (IPPM) processes flowed down from the buyer, in this case, the Federal Government. This can be the confidence in the estimate for any variable. IEEE Transactions on Engineering Management , 57 (4), pp. IN this case Mean Time To Failure.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

MPUG

MAY 14, 2021

Please send those over at any time using the chat question box on the “go to webinar” control panel where we do plan to answer those questions for you throughout the session today. Having spent half my life in the commercial space and half in the government space, the questions are always there. What’s happening now.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Herding Cats

FEBRUARY 9, 2018

I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

nTask

AUGUST 8, 2019

As the name suggests, Waterfall focuses on planning the lifecycle of the project by dividing the project into distinctive, separate and exclusive parts: In a Waterfall model, each phase must be completed before the next phase can begin. . In his presentation he described the use of such phases in software engineering.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What Resources will be needed to reach Done?

Transportation 28

Transportation Software Engineering Finance 2011 28

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. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

JANUARY 13, 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. Estimates of cost, schedule, technical performance on the left have a lower probability of being precise and accurate than estimates on the right.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 28

Herding Cats

MAY 11, 2019

requires making estimates) ? Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 9, 2017

DeMacro made this post, which has been picked up by the agile community to mean estimating is a waste. . Implying there is no need to measure the project performance and by implication no need to estimate. For example in "Software Engineering: An Idea Whose Time Has Come and Gone?" All estimates are evil.

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

Herding Cats

JULY 28, 2017

This was my starting point for becoming a software engineer rather than a physicist, by the way. . You're bad at estimating - WHY? Estimating Processes in Support of Economic Analysis. Estimating and Making Decisions in Presence of Uncertainty. Why Guessing is not Estimating and Estimating is not Guessing.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

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 Cone IS the Planned reduction of uncertainty as the project proceeds.

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 Cone IS the Planned reduction of uncertainty as the project proceeds.

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). Estimates are needed but are subject to large level of uncertainty.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

FEBRUARY 23, 2016

The conjecture that we can make decisions in the presence of uncertainty without estimating the impacts of those decisions is without any principles that can be tested beyond personal anecdotes of I know people who spend other peoples money without providing estimates. Not a group that likes to get questions, by the way.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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). Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

JUNE 19, 2017

These activities, their releationships and values are defined in a PLAN for increasing the probability of success for the project. The creation and management of the Plan is usually performed by the Program Planning and Controls group where I work. . Framing Assumptions for the Cone of Uncertainty .

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JUNE 7, 2018

The Design Structure Matrix (DSM) method, was introduced by Steward in for task-based system modeling and initially used for planning issues. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . Allen School of Computer Science Software Engineering Course .

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 7, 2018

The Design Structure Matrix (DSM) method, was introduced by Steward in for task-based system modeling and initially used for planning issues. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . Allen School of Computer Science Software Engineering Course .

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

MPUG

MAY 6, 2021

We do plan to answer your questions throughout the session today. We are a consulting company in the DC Baltimore area that specializes in project and portfolio management for about 80% of our customers in the government space, the other 20 in the commercial space. Kyle: All right, we’ll go ahead and get started.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

MPUG

JULY 16, 2021

You’ll notice in the far left, you have your requirements planning process. Where you’re going to be iteratively planning your monitoring and controlling. Of course, there are other aspects to this requirements planning that we talked about in the first presentation. How are you going to do that?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

MPUG

OCTOBER 15, 2020

For example, prioritizing the product backlog or refining the product backlog, doing an own value management with respect to the product backlog or estimating, or having the various project accounting principles with respect to product management. Even the engineers, hardware engineer, software engineer, mechanical engineer.

PMI 52

PMI Certification Software Review Technical Review 52

Teamweek

DECEMBER 8, 2023

The global economic consequences of this mismatch were estimated to be ~$8 trillion in unrealized GDP for the world economy in 2018. For instance, an individual having a software engineering degree might not be a great fit for a customer service role. Skills mismatches cost organizations billions of dollars worldwide.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Teamweek

NOVEMBER 9, 2022

The first way to look at project management software is based on what you’ll use it for. Some common use cases include: Project planning Resource management Portfolio management Process management. Let’s look at these types of project management software in detail. Project and resource planning software.

Software Review 52

Software Review Software Technical Review Construction 52

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. The same rule of thumb applies to other governance reviews, as well. Test data must be crafted to align with test cases so that every execution of a test plan is identical. It needs to go away.

Software Review 78

Software Review Software Technical Review Development Team Review 78