Herding Cats

JUNE 9, 2018

With these business principles of software development and projects in general, we can ask and answer five principles of project success. What is the Plan to reach done at the needed time for the needed budget, with the needed outcomes? What dos Done look like in units of measure meaningful to the decision makers?

Transportation 28

Transportation Software Engineering Finance 2011 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

Herding Cats

JANUARY 13, 2017

Barry Boehm's work in “Software Engineering Economics”. When you hear I have data that shows the uncertainty doesn't reduce , then that project is out of control and will be late, over budget, and likely not perform to the needed effectiveness and performance parameters. Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 28

Herding Cats

MAY 10, 2019

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. Planning, Tracking, and Reducing Complex Project’s Value at Risk,” Tyson R.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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." . Let's start with the obvious.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

MAY 11, 2019

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. Planning, Tracking, and Reducing Complex Project’s Value at Risk,” Tyson R.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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." . So how do we get ±10% accuracy?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

FEBRUARY 9, 2018

We can estimate the total cost, total duration, and the probability that all the Features will be delivered on the program we are working for the US Government. Or ANY software project for that matter. Showing up late, over budget, and with missing Capabilities is not what the customer paid for. Let's Look at What a Forecast is.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's some examples of Planned variances and managing of the actual variances to make sure the project stays on plan. In this case, the projected base weight is planned and the planned weights of each of the major subsystems are laid out as a function of time.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. 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”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. 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”. Inadequate assessment of risks and unmitigated exposure to these risks with proper handling plans. Unanticipated technical issues with alternative plans and solutions to maintain effectiveness. The notion of the Cone of Uncertainty has been around for awhile.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

FEBRUARY 23, 2016

This Does Not Scale - If there are software development projects that can be executed without knowing how much it will cost in the end (an open ended spend plan), or projects where the budget is capped (a Not To Exceed Number) and we don't really need to know the upper bound of the features to be delivered, how large can this notion scale?

Estimate 39

Estimate Risk Management Finance Software Developers 39

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. . What is the Plan to keep the temperature in the room at 76 degrees?

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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? Can you afford it?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

Teamweek

DECEMBER 8, 2023

For instance, an individual having a software engineering degree might not be a great fit for a customer service role. Or, they might have decent design skills but lack other hard skills needed to accomplish projects within budget using the tools your clients require. Here’s an example of talent or skills gap analysis.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Leading Agile

NOVEMBER 29, 2023

Our new COO, Philippe Bonneton, and Mike Cottmeyer sit down to discuss the challenges associated with moving monolithic legacy applications into the cloud and how an iterative and incremental change model can help you plan out a cloud migration and ensure success. You’re not just a strategy firm. But that was after the fact.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Leading Agile

NOVEMBER 29, 2023

Our new COO, Philippe Bonneton, and Mike Cottmeyer sit down to discuss the challenges associated with moving monolithic legacy applications into the cloud and how an iterative and incremental change model can help you plan out a cloud migration and ensure success. You’re not just a strategy firm. But that was after the fact.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

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

It’s often considered good practice to involve security specialists early in each project, rather than waiting until most of the time and budget have been used up before they have a chance to perform a review. The same rule of thumb applies to other governance reviews, as well. It needs to go away.

Software Review 78

Software Review Software Technical Review Development Team Review 78