Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. 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. reducible and irreducible ?

Risk Management 38

Risk Management Risk Technical Review 2002 38

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). Prentice-Hall, 1981. This is due to many reasons.

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). Prentice-Hall, 1981. This is due to many reasons.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

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) ? De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

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. So the question is? -

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Scrum.org

FEBRUARY 4, 2022

What is the optimal size of a team? Should teams be stable over at least several years, or is it a good idea they change at will? How should leadership interact with autonomous teams? Is scaling always a bad idea? Of all the impediments that a team faces, which is the one to focus on first?

Agile 204

Agile Software Review Underperforming Technical Team Technical Review 204

MPUG

JULY 16, 2021

Please find below a transcription of the audio portion of Walter Stinnett’s session, Monitoring and Controlling Requirements, being provided by MPUG for the convenience of our members. This presentation, we’ll be discussing, monitoring and controlling requirements. Which of the following is not a change control tool or technique?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

MPUG

MAY 6, 2021

Kyle: If you have any questions during today’s presentation, please send those over at any time using the chat question box on the go to webinar control panel. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. What does the team care about?

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

JUNE 12, 2018

This is simply good process development and management. Then conjecture that NOT estimating will fix that symptom. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. Principle #1 - Trust Your Process, or Change Your Process.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

JUNE 12, 2018

This is simply good process development and business management. Then conjecture that NOT estimating will fix that symptom. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. And the practices are not connected to any principle.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

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. Avaramidlis and J.

Estimate 40

Estimate Software Review Software 2012 40

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

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. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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 2006 2005 2013 64

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. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's .

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

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. This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's .

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

MPUG

OCTOBER 15, 2020

If you do you have any questions during today’s session, please send those over at any time using the Chat Question Box on the Go-To Webinar control panel. You’ll be knowing DS DNE, which is Development in Northern Europe or you will be knowing about BDD, which is Behavior Driven Development. Then team members.

PMI 52

PMI Certification Software Review Technical Review 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. First, there’s a tool-centric mentality about software-related work. Try installing a typical business application on a pristine development environment. Requirements & validation.

Software Review 78

Software Review Software Technical Review Development Team Review 78