Herding Cats

AUGUST 1, 2018

“The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model,” Da Yang, Barry Boehm, Ye Yang, Qing Wang, and Mingshu Li, ICSP 2007 , LNCS 4470, pp. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

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. Dorofee, et.

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) ? reducible and irreducible ?

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

JULY 7, 2018

When this deciding takes place in the presence of uncertainty, we are not able to connect the causes found in the past with the effects that are possible in the future without estimating these possible connections between cause and effects [1].

2007 30

2007 Estimate Software Developers Software Development 30

Herding Cats

NOVEMBER 18, 2017

In software this is a HUGE mistake! A requirement is a statement that identifies a product or processes operational, functional, or design characteristic or constraint, which is unambiguous, testable, or measurable and necessary for product or process acceptability (ISO 2007). 1] Software Engineering Body of Knowledge, [link] . [2]

2007 31

2007 Software Engineering Engineering Manufacturing 31

Herding Cats

JULY 7, 2018

When this deciding takes place in the presence of uncertainty, we are not able to connect the causes found in the past with the effects that are possible in the future without estimating these possible connections between cause and effects [1].

2007 28

2007 Estimate Software Developers Software Development 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

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 BLUE bars are the probabilistic ranges of the current estimate date.

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 BLUE bars are the probabilistic ranges of the current estimate date.

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

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. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty.

2003 46

2003 2014 2015 2011 46

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Software development is (generally speaking) very complex. Why our brain is not built for software engineering. Limitations of attention.

2002 202

2002 SCRUM 2007 2003 202

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. Of late, Cone of Uncertainty has become the mantra of No Estimates advocates claiming that data is needed BEFORE the Cone is of any use.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

DECEMBER 4, 2017

Measures of Performance - are performance measures that characterize physical or functional attributes relating to the system operation, measured or estimated under specific conditions. Reinventing Project Management , Aaron Shenhar and Dov Dvir, Harvard Business Press, 2007. Measures of Performance. Let's look at the differences.

2005 37

2005 Performance Measurement Closing Controlling 37

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. 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." Macroeconomics is not. .

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Scrum.org

AUGUST 17, 2020

People often fail to understand this fallacy because they underestimate how much of their behavior and their outcomes are influenced by randomness (Taleb, 2007). When teams estimate work, hearing an initial estimate is likely to “anchor” further estimates. How to reduce this bias. Examples in the workplace.

2015 221

2015 2014 2004 Influencer 221

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. Performance Evaluation of non?

Estimate 40

Estimate Software Review Software 2012 40

Epicflow Blog

JANUARY 12, 2021

As, for example, an IT project manager orchestrates IT projects and leads corresponding teams in their software development efforts. Paper presented at PMI® Global Congress 2007—North America, Atlanta, GA. Healthcare project manager; Finance project manager; Insurance project manager; Utility project manager, Legal project manager.

PMO 82

PMO 2007 Controlling Construction 82

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. 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. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Scrum.org

DECEMBER 23, 2021

Why do software teams?—?despite 2012, Li & Shatnawi, 2007). The researchers also cleverly used issue tracking data to estimate developer workload and where the commit was on a timeline from the conception of the project to the present day. . Why is code quality so often an issue? despite their best initial intentions?—?often

Software Review 183

Software Review Technical Review Underperforming Technical Team 2015 183

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

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

MPUG

JUNE 30, 2019

Microsoft Project is a software application sold by Microsoft that provides project management tools to manage projects. Organize, estimate, and schedule work, resources, and costs to ensure projects are completed according to plan. The software is automatically kept up to date (with options for customizable policies).

2010 100

2010 2013 2016 2019 100

Paymo App

DECEMBER 11, 2017

To print these invoices you should be using Microsoft Office 2007 or a newer version so that their format will display correctly. Editing these templates involves already having another software to complete the personalization process. Project management software. Here are the top 3 advanced solutions we’ve found for you: 1.

Finance 51

Finance 2007 Construction Innovation 51

MPUG

NOVEMBER 14, 2019

And during the 2007 and 2003 versions, we got a new way of creating reports. In 2007, it became in color. And please take note that we have resources in here, we have estimated work, we have duration, we have some completed tasks. But then Microsoft Project evolved. And it would transform that to an analytical cube.

2013 40

2013 Finance 2007 Software Review 40

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software. Am I getting the velocity?

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Planio

JULY 22, 2020

If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. However, while this book covers basics like estimating and planning projects, where it shines is in covering the soft skills of project management.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Resource Guru

JUNE 23, 2023

We’re here to help you evaluate and choose the best software that will help enable growth at your agency. To execute the best project management for agencies, switch to purpose-built agency software. Look for customization options that allow you to tailor the software to your agency’s specific needs and workflows.

Software Review 52

Software Review Technical Review Software 2021 52

MPUG

OCTOBER 24, 2019

Can we actually zero in on making sure we get to clarity, and the idea of producing value where we can actually see working software or a working solution, or doing some sort of a progressive elaboration of work and work that goes together. I can kind of plan and estimate. What’s deeper estimates?” What’s done?

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40