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

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

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 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

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 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

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. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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). Economics of Software Development. Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

MARCH 4, 2017

Let's start with a clear and concise description of the problem of successfully managing projects in the presence of uncertainty: Accurate software cost and schedule estimations are essential for non-trivial software projects. As a software project progresses, more information about the project is known.

2010 28

2010 2007 Estimate Aerospace 28

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

ProjectManager.com

JANUARY 12, 2022

Nowadays, even non-PMP-certified workers are taking on work that closely resembles a traditional projects, and the desire to manage them better is growing every year. What to Expect: Sessions focus on agility, software engineering and lean business. AIPM National Conference. 10th IPMA Research Conference. Agile 2022. Future PMO.

2022 285

2022 Technical Review PMO Underperforming Technical Team 285

Scrum.org

FEBRUARY 4, 2022

Perhaps you’ve read many blog posts about how horrible SAFe is, or how useless estimation is, or what the optimal size of a team is. What if you recommend teams to stop estimation altogether and cause financial damage compared to when you wouldn’t have recommended this? You may have the practical experience to support your beliefs.

Agile 192

Agile Software Review Underperforming Technical Team Technical Review 192

MPUG

MAY 6, 2021

I came to my office today because I was having internet issues at home, and so I will ask for your indulgence because our office is actually quite close to a hospital. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. By education and training.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. Then conjecturing (here) that Not Estimating will somehow fix the problem of when you are DSTOP. We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level. But the simplest way to answer is .

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. The notion of waterfall development on slide 9 as actually prohibited in our domain. Then conjecturing (here) that Not Estimating will somehow, through some unstated process of correction or prevention, fix the problem of when you are DSTOP. Not likely.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team 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

APRIL 4, 2019

It just closed the loop faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

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. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. We develop these reference classes using Agile Function Points. 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

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 55

Software Review Software Technical Review Development Team Review 55