Scrum.org

MARCH 16, 2020

I believe Agile software development is more than ready to use new forecasting techniques to express uncertainy to narrow their decision-making process. These new forecasting techniques are not based on estimations but historical data, thus saving time on the part of developers to focus on what they do best.

Agile 192

Agile Underperforming Technical Team 2030 Estimate 192

The IIL Blog

MAY 17, 2023

We have read books and journal articles on various project management topics. Systems development projects, especially those with a large software component, would spend years gathering requirements, designing, and building a system that would be plagued by changes and completely outdated by the time it was launched.

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Increasing the Probability of Success , Dallas MPUG, May 6th, 2009.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

MAY 10, 2019

5887, 2009. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. 532, August 2009. Risk a Feelings,” George F. Loewenstein, Elke U.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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 ? Verhoef, Science of Computer Programming, Volume 74, Issues 11–12, November 2009, Pages 934-988. Related articles.

2012 48

2012 2007 2011 2010 48

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. 5887, 2009. 532, August 2009. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. The chief critic of the cone has data collected from his projects that develop Products. From his article in an IEEE magazine often quoted by No Estimates advocates. .

2007 34

2007 2012 2009 2010 34

Herding Cats

DECEMBER 28, 2017

The use of estimating in software development project mandates those estimates be updated with actual performance data to have any credibility in the construction of the Estimate to Complete and Estimate at Completion. Economics of Software Development. The Economics of Software Quality. Related articles.

2009 40

2009 Estimate Software Developers Software Development 40

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 27, 2016

There are two kinds of uncertainty on all projects, no matter the domain, including software development projects. The process of making a decision involves three elements: values, alternatives, and facts (Buede, 2009). [1]. Related articles. The Notion of Enterprise Software Development.

2009 28

2009 2015 Influencer Performance Measurement 28

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

Online PM Courses

SEPTEMBER 16, 2018

And in this guide, I will share everything I have found out, in my longest article ever. This article is a companion to our earlier guide: ‘Project Management Qualification: Should I or Shouldn’t I?’ In 2009 Ken Schwaber left Scrum Alliance to build his own Agile certification, PSM (Professional Scrum Master), at scrum.org.

Certification 114

Certification Agile Prince2 PMI 114

Herding Cats

JANUARY 22, 2017

The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1st Flight Article). Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1st Flight Article). Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1 st Flight Article). Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

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. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

FEBRUARY 23, 2016

This list starts with the earliest posts, beginning in 2009. . New Books for Work - making multiple decisions, forecasting and simulating software development projects, forecasting methods and applications. How to Estimate Software Development - Update. Estimating Software-Intensive Systems.

Estimate 39

Estimate Risk Management Finance Software Developers 39

MPUG

SEPTEMBER 9, 2020

Satya N Dash: In addition to that, I have seen management practitioners when they create a plan, they make a lot of mistakes, without any software tool, in this case Microsoft Project. As early as 2009, 2010, nearly 11 years before I was working as a PMO. One is a software developer. ” It is exactly the reverse.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

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

MPUG

NOVEMBER 14, 2019

And you would have the option to include your own set of report templates, which would be on a certain location such as the TPC articles, MPUG articles, and then I would have the XL reports there. And let’s see that live in action, where I click on new, and I click on for instance, a software development plan.

2013 40

2013 Finance 2007 Software Review 40

Leading Agile

JUNE 20, 2018

In an article in Forbes , Steffan Surdek offers three key characteristics (paraphrased here): has a certain level of decision-making authority. ” The purpose of that article is to discuss misconceptions about self-organizing teams, and yet it begins with a rather shaky definition of the term. Let’s keep looking.

Agile 102

Agile Defining 2001 2009 102