Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. Peter Drucker (1975) Management (From The Principles of Software Engineering , Chapter 6, Tom Glib, 1988). Without these estimates, there is no risk management. Capabilities Based Planning.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

NOVEMBER 3, 2016

Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do. There is no discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately. illities are a waste.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

Planio

JUNE 8, 2022

Instead, anyone can make the shift with a bit of research and an action plan. A technical project manager needs to be proficient in standard project management skills like time management, leadership, communication, decision-making, and planning. Estimate the time, effort, and resources for an entire project.

Technical Review 78

Technical Review Software Review Development Team Review Underperforming Technical Team 78

Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? As more details get developed, the Cone converges to the actual value. Steve McConnell.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? An estimate is. It's a fallacy.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. Our knowledge of this world - the planned and actual behaviors of the project. All estimates have precision and accuracy. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

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

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. A final Thought . Flyvbjerg, H.

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. This letter states.

2007 34

2007 2012 2009 2010 34

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

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. There was a classic #Noestimates post this week that said.

2008 32

2008 2002 Estimate Software Engineering 32

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

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. A final Thought . Flyvbjerg, H.

Transportation 28

Transportation Software Engineering Finance 2011 28

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

AUGUST 1, 2018

Reducing Estimation Uncertainty with Continuous Assessment: Tracking the 'Cone of Uncertainty’” Pongtip Aroonvatanaporn, Chatchai Sinthop and Barry Boehm, Center for Systems and Software Engineering University of Southern California , Los Angeles, CA 90089, ASE’10 , September 20–24, 2010, Antwerp, Belgium, 2010. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Epicflow Blog

MAY 14, 2019

Create a Solid Project Plan and Clear Business Case. Creating a clear business case and a critical path that designs your plans can help you plan well. Being attentive to the needs of your sponsor from the very beginning of your project also enhances the effectiveness of planning: “What is the main cause for project failure?

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Workzone

JANUARY 18, 2023

You can re-arrange the pieces to make them fit to your whims, or project plans that is. Favro Gamers or rather game developers, you may want to check out Favro. It’s specifically built for technicl creatives—such as game developers, UX designers and software engineers. Pricing: $25-$118/month for 5 users 5.

2023 52

2023 Software Review Lean Estimate 52

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

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

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

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. These activities, their releationships and values are defined in a PLAN for increasing the probability of success for the project.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

MARCH 4, 2017

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. All project work operates in the presence of uncertainty.

2010 28

2010 2007 Estimate Aerospace 28

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. By education and training, I’m actually a software developer. The blue line here is the plan. Is it Fletcher? Is it Eric?

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

ProjectManager.com

JANUARY 12, 2022

What to Expect: This three-day event focuses on the importance of planning, scheduling and how to manage scope. There will be breakout sessions on using project management tools and techniques to help with more accurate estimates, how to keep projects on track and on evaluation of project performance. The Resource Planning Summit.

2022 276

2022 Technical Review PMO Underperforming Technical Team 276

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

LiquidPlanner

JANUARY 18, 2023

Agile came about in the world of software development precisely because people started to realize that the pace of change had become so fast that it was smarter to embrace that change and find ways to work within it than try to resist. It describes four values for software development. No change in engineering practices.

Fractional VPE 148

Fractional VPE Agile Software Review 2001 148

MPUG

MAY 6, 2021

We do plan to answer your questions throughout the session today. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. That’s just it.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. This will affect all estimates and predictions. This will affect all estimates and predictions. Their article inspired me to apply the same insights to Scrum and to extend it with my own.

2002 192

2002 SCRUM 2007 2003 192

nTask

SEPTEMBER 9, 2021

When we talk about software project management in a conversation related to the organizational paradigm, it usually comprises of all of the things from software development, documenting the whole process, testing every single element, and delivering the finished product on time. Different Types of Software Project Management.

2021 157

2021 Software Review Software Software Developers 157

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. The supposed evidence in the presentation, that estimating "does not work" starts with the Chaos Report. Principle #2 - Shorten the Feedback Cycle .

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

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

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 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. The notion of waterfall development on slide 9 as actually prohibited in our domain. This is called Doing Stupid Things on Purpose (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