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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

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

Risk Management 35

Risk Management Risk Technical Review 2002 35

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100

MPUG

MAY 14, 2021

By education and training, I’m actually a software developer. I got junior software engineers, software engineers, senior software engineers. I know I’m going to have a senior software engineer and I want him working on these tasks [inaudible 00:12:15] who that is.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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. Closed Loop Stochastic Adaptive control in the presence of Evolving Uncertainty. The definition of a TPM is on page 14. . .

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”. Here's a simple definition of the Cone of Uncertainty: . This is a closed loop control system for managing the program with a T echnical Performance Measure (TPM). The notion of the Cone of Uncertainty has been around for awhile. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's a simple definition of the Cone of Uncertainty: . This is a closed loop control system for managing the program with a T echnical Performance Measure (TPM). The notion of the Cone of Uncertainty has been around for awhile. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Here's a simple definition of the Cone of Uncertainty: . This is the paradigm of the Cone of Uncertainty - it's a planned development compliance engineering tool, not an after the fact data collection tool. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

FEBRUARY 9, 2018

This is usually a cost, a completion date, a performance measure used in a closed loop control system to keep the project GREEN while delivering the needed Capabilities to produce the Value for the customer at the needed time for the needed cost. First a definition. Then as we say in our domain. Someone has to be the adult in the room.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Herding Cats

MARCH 4, 2017

Before going let's look at the definition of the Cone of Uncertainty because it is misdefined and misused by some [4] in Wikipedia. Software development project schedule estimation has long been a difficult problem. This approach ignores the core principle of closed loop control. Four sample causes are shown below. .

2010 28

2010 2007 Estimate Aerospace 28

Scrum.org

FEBRUARY 4, 2022

There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. The same goes for strong claims like “Scrum Teams should not use a Definition of Ready” or “SAFe destroys autonomy”. Closing Words. That is great!

Agile 183

Agile Software Review Underperforming Technical Team Technical Review 183

Leading Agile

JUNE 27, 2018

” I was reminded of the old joke by a recent article by John Regehr, Professor of Computer Science at the University of Utah, entitled “Closing the Loop: The Importance of External Engagement in Computer Science Research.” This is not an isolated case, and most of what passes for research in software engineering is horrible.

Software Review 94

Software Review Technical Review Underperforming Technical Team 2007 94

Leading Agile

OCTOBER 22, 2018

In the 1960s, it was considered a baseline good practice in software engineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.

Software Review 77

Software Review Infrastructure Engineering Executing 77

Leading Agile

JUNE 18, 2018

People who specialize in testing software will need technical skills more-or-less on par with competent software engineers. Open/Closed. Clear definitions of expectations on both sides might sound like a good way to ensure distributed systems behave according to design, but there are limitations. Authoritative.

Software Review 83

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 83

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 is a closed loop system optimization process applied to all the projects we work. And money in the bank is what software development is about. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Teamweek

OCTOBER 20, 2022

You probably already know—Agile isn’t just for software developers anymore. After all, Agile projects deliver proven value in software projects: Higher profit More meaningful projects and client relationships Greater productivity Clearer communication. Takes place “behind closed doors” and is closely based on original specs.

Agile 52

Agile Technical Review SCRUM Executing 52

Planio

FEBRUARY 10, 2021

We’re definitely biased, but we think Planio could be the best project management tool for you. The original online show-and-tell platform for the design community, Dribbble now hosts close to half a million design portfolios. However, just because Jira is great for project managers doesn’t mean it’s equally loved by developers.

Technical Review 167

Technical Review Software Review Software Developers Software Development 167

Leading Agile

FEBRUARY 12, 2024

Today, we take a look at why your software isn’t soft, explore the challenges of writing code at scale, and discuss a modern approach to writing code that will maintain its safety and simplicity over time. Video Transcript Chris Beale In traditional software development. So anything can be architecture.

Software 69

Software Underperforming Technical Team Governance Government 69

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. Two closely related conceptual errors appear to be quite common. First, there’s a tool-centric mentality about software-related work. The company wanted to automate their dispatching process.

Software Review 60

Software Review Software Technical Review Development Team Review 60