Herding Cats

MARCH 17, 2019

Business, Technical, Systems, Risk, and Project Management. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

NOVEMBER 12, 2016

Loss of control creates risk of failure. Compensate for cost variation by including risk reduction metrics. Alleman, "Product & Process Development Kaizen for Software Development, Project, and Program Management, LPPDE, Denver Colorado, April 2008. [5] Embrace objectivity. Not improving fast enough.

Agile 61

Agile 2008 2009 2011 61

The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. As IT became mainstream in the latter half of the 20 th century, so did several job roles within the industry.

2001 78

2001 2007 Information Technology 2005 78

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Planio

JULY 22, 2020

Risk Up Front: Managing Projects in a Complex World. 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. Published date: 2008 (revised edition). Author: Brett Harned.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

OCTOBER 15, 2017

I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. the Secretary of Defense shall develop and implement a new acquisition process for information technology systems.

Process 39

Process Agile 2011 Aerospace 39

Herding Cats

JUNE 25, 2016

Theory of Decision under Uncertainty, Itzhak Gilboa, July 2008. Managerial Decision Making Under Risk and Uncertainty Ari Riabacke. Software development decision making is a well studied subset of that field. This is a core premise of #NoEstimates from the Original Poster. Decision Analysis for the Professional.

2008 44

2008 Estimate Finance Software Development 44

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Agile Software Development (#ASD). Business, Technical, Systems, Risk, and Project Management. Those lessons are directly transferable to the management of software development teams.

Technical Review 42

Technical Review Performance Measurement 2003 Government 42

Herding Cats

APRIL 13, 2018

This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. If you google "Real Options software development" or "real options ICT" you'll find these and many dozens more. 72, 2nd Quarter, 2008, pp. 72, 2nd Quarter, 2008, pp.

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Agilemania

MARCH 22, 2021

With traditional plans, you’ll always have the risk of delayed product delivery. Although introduced in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka through paper, they published (New New Product Development Game) and followed by agile manifesto in 2001. Eventually, you’ll become uncompetitive on the market.

Agile 52

Agile 2001 2008 Software Review 52

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . Armour, Communications of the ACM , March 2008, Vol.

2007 42

2007 2012 2006 2008 42

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty.

2002 34

2002 2008 Technical Review Software Review 34

Teamweek

JUNE 25, 2020

Asana was founded in 2008 by ex-Google and ex-Facebook engineers with the aim to make team collaboration better. It comes with project, task, resource, and risk management, time tracking, and team collaboration. 3 Reasons Why You May Want To Look At Asana Alternatives. While really powerful, Asana is not for everyone. as add-ons.

Underperforming Technical Team 97

Underperforming Technical Team Software Review Planning Development Team Review 97

Herding Cats

SEPTEMBER 25, 2018

Estimates of the aleatory and epistemic uncertainties that create risk to the delivered Value need to be handled. The handling of the risks created by these uncertainties and the residual risk still present after the handling is complete need to be part of the assessment of the alternatives. Sjacter and Mark A.

2009 34

2009 Artificial Inteligence 2013 2005 34

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. IT Risk Management.

2007 34

2007 2012 2009 2010 34

Herding Cats

OCTOBER 20, 2017

For software development systems like Kanban, which is production line-centric, Litle's Law tells us. λ = average production rate of complete software components. λ = average production rate of complete software components. There are two fundamental assumptions for Little's Law to work in the software development domain".

Underperforming Technical Team 34

Underperforming Technical Team 2008 Estimate 2011 34

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. taken from [3]).

Software Review 34

Software Review Technical Review Estimate Software Development 34

Herding Cats

JULY 8, 2018

This advocate continually confuses Macroeconomics of financial markets and sovereign finance with Microeconomics of software development. Here's a book review from 2008, about Black Swans and Fooled By Randomness in the context of managing software development in the presence of uncertainty.

2002 28

2002 2008 Technical Review Software Review 28

Herding Cats

JANUARY 22, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

SEPTEMBER 19, 2018

Monte Carlo simulation on projects examines all paths through the network of activities or all possible states of the project for the duration, cost, and risk that create impacts on duration and cost. Monte Carlo and Agile Development . 7] "Fuzzy Monte Carlo Simulation and Risk Assessment in Construction," N. 335 - 341. [7]

2010 43

2010 Technical Review Estimate Software Review 43

Herding Cats

FEBRUARY 4, 2017

Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. This is done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2004 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. reducible and irreducible ?

Risk Management 35

Risk Management Risk Technical Review 2004 35

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc. 61, September 2004. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Teamweek

MAY 21, 2020

Are there any constraints or risks? Trello started in 2011 as a tool for software development teams. Asana was founded in 2008 by ex-Google and Facebook engineers. To do things that matter, you only need to focus on three types of project activities. Project planning. What are the deadlines, milestones, and goals?

2020 52

2020 Planning Software Review 2011 52