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

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

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. All estimates have precision and accuracy. Deciding how much precision and accuracy is needed for a credible estimate is critical to the success of that decision.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 14, 2018

Software development is a Value Creaton activity, but Value cannot be determined unless we know the cost to produce that value and when that value will be available for use by those who of paid for that Value. For software development, those scarce resources are people, time, and money. Microeconomics .

Process 45

Process Estimate Software Developers Software Development 45

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

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

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

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

Epicflow Blog

MAY 14, 2019

Ken Stafford , an Independent Consultant at Ken Stafford Project Support Services, also talks about the perks of having a powerful project plan: “ Solid planning, [a] well defined critical path and controlled interfaces are so important as a base, but I have found they support, more than define, project success.”.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

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

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

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). Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

MARCH 4, 2017

Are the upper and lower control limits of each measure inside the planned acceptable performance range at any specific point in time on the path to Done? In many cases, once the estimates have been made (at proposal or authorization to proceed), recalibrate and reduction the uncertainty of the initial estimates is not always performed.

2010 28

2010 2007 Estimate Aerospace 28

Workzone

JANUARY 18, 2023

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. Their Kanban board stretches horizontally across to help you visualize what’s next in the product development cycle.

2023 52

2023 Software Review Lean Estimate 52

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. Kyle: Do you have any questions during today’s presentation?

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Scrum.org

AUGUST 18, 2023

In the realm of software development, principles of DevOps and a commitment to technical excellence can further enhance the process. Originating from lean manufacturing principles, VSM's relevance has expanded, becoming a cornerstone in fields such as software development.

SCRUM 166

SCRUM Software Review Technical Review Software Engineering 166

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 204

Agile Software Review Underperforming Technical Team Technical Review 204

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 212

2002 SCRUM 2007 2003 212

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

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. By education and training.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

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 sampling rate to maintain control must be matched with the processes change rate. The notion of waterfall on slide 9 as actually prohibited in our domain.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

nTask

AUGUST 8, 2019

Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

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

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

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

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. I'm not expecting anyone to read all these books.

Risk Management 43

Risk Management Risk 2003 2011 43

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. Almost impossible?

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. Is this normal?

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

Teamweek

NOVEMBER 9, 2022

Project tracking software helps you: Understand if you’re on track to meet task, milestone, and project deadlines Time tracking Compare estimated vs. actual efforts and costs Adjust plans quickly if you’re not on schedule or within the budget. Workflow management software. Example: OrangeScrum. Example: Traction.

Software Review 52

Software Review Software Technical Review Construction 52

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . We always want to minimize the number of interfaces between modules, minimize the complexity of each interface, and control the type of info flow. Highly coupled have program units dependent on each other.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . We always want to minimize the number of interfaces between modules, minimize the complexity of each interface, and control the type of info flow. Highly coupled have program units dependent on each other.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

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. They also assign estimates to each task. “We’re an Agile agency ??.”.

Agile 52

Agile Technical Review SCRUM Executing 52