Herding Cats

APRIL 4, 2019

It just closed the loop faster. 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. Misconceptions of Risk , Terje Aven, John Wiley & Sons, 2010. This is good, but it doesn't reduce risk. Alexandre Vidal, Springer?Verlag,

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MARCH 11, 2017

Accuracy - how close is the estimate to the actual value? So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date.

2003 46

2003 2014 2015 2011 46

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. 255, April 2010. 24, 2010. “A Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Project Pulse Journal

MARCH 25, 2024

A software development team may use dashboards showing alternative solutions, connected marketing strategies, user personas, customer problems, or frameworks prioritizing features based on data, user stories, and the existing product. Sustainable living plan 2010 to 2020: Summary of 10 years’ progress. 2020, May).

Sustainability 52

Sustainability Development Team Review Innovation 2024 52

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. Simulations should be run in environments that are as close to realistic as possible.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Scrum.org

JUNE 5, 2019

Agile software development started with developers. Agile software development was started by developers. Starting out with a strong focus on website development, I built my first site for them in 2002, first as a freelancer later as an employee. NowOnline started somewhere in 2001.

SCRUM 138

SCRUM 2002 2003 2001 138

Herding Cats

SEPTEMBER 19, 2018

The result is an artificial world (model) that is meant to closely resemble the real world in all relevant aspects. [8]. This is a Closed Loop Control Systems for managing the performance of a Software Intensive System of Systems, all developed using Scrum. Monte Carlo and Agile Development . 335 - 341. [7]

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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. . Thesis, George Mason University, 2010. "An

2007 42

2007 2012 2006 2008 42

Herding Cats

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software development is a non-ergodic process.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

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

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Open Loop / Closed Loop Project Controls - project management is a closed loop control system. A steering target is established, actions are taken, variances are assessed, corrective actions are taken to close the loop. Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MARCH 4, 2017

Software development project schedule estimation has long been a difficult problem. Instead, it suggests the Cone of Uncertainty is not the proper model for software estimating, with no evidence other than anecdotal examples from observed projects. This approach ignores the core principle of closed loop control.

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

JANUARY 22, 2017

The planned value, the upper and lower control limits, the measures of actual values form a Close Loop Control System - a measurement based feedback process to improve the effectiveness and efficiency of the project management processes by [1]. 6] " Open Loop / Close Loop Project Controls ". [7] Software Engineering Economics”.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The planned value, the upper and lower control limits, the measures of actual values form a Close Loop Control System - a measurement based feedback process to improve the effectiveness and efficiency of the project management processes by [1]. 6] " Open Loop / Close Loop Project Controls ". [7] Software Engineering Economics”.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

This is the basis of Closed Loop Project Control Estimates of the needed reduction of uncertanty, estimates of the possisble reduction of uncertainty, and estimates of the effectiveness of these reduction efforts are the basis of the Close Loop Project Control System. 6] " Open Loop / Close Loop Project Controls ". [7]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. His book on Kanban , published in 2010, is still one of the most comprehensive resources out there for technology-focused projects. A service project to resolve bugs and close-out customer tickets.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Project Management Hacks

AUGUST 4, 2016

Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I recall a project where we were close to going live. I led an effort to develop a risk-based software development process. Editor’s Note: Rita Mulcahy passed away in 2010.

2013 28

2013 2003 Technical Review 2010 28

MPUG

MAY 24, 2020

I’ve been working on creating blog posts and videos and giving speeches since 2010. Some of them are going to be really close to what we see. Raphael Santos: So software development projects they basically respond, or they are accountable for 102,000 hours out of those 122 hours.

Software Review 40

Software Review Artificial Inteligence Software Developers Software Development 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.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

Leading Agile

NOVEMBER 17, 2020

So we first worked together, I guess it was probably back in like late 2009, 2010. Talk to me about some of the challenges that you had taking it straight from a software development perspective. I wasn’t actually trying to help anybody get better at software development per se, or product management per se.

Technical Review 86

Technical Review Software Review Agile Governance 86

MPUG

OCTOBER 16, 2019

That is a best practice is to be as close to the customer or the person who is actually viewing and defining what is the stakeholder that I want or what I’m representing. We want to keep them as close to the team that’s building. Did you want to close? Tim Runcie: I’m so close here. That is great.

Agile 40

Agile Technical Review Software Review Engineering 40

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. Satya N Dash: Great.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

MPUG

JULY 23, 2020

He has extensive experience of both project management, and software development. Previous positions have included VP of development for Welcom, senior director for product management at Deltek, and manager for computerized project management at Worley engineering. Anything else before we close out today, John?

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52

MPUG

JULY 23, 2020

He has extensive experience of both project management, and software development. Previous positions have included VP of development for Welcom, senior director for product management at Deltek, and manager for computerized project management at Worley engineering. Anything else before we close out today, John?

Risk 52

Risk Software Review Estimate Underperforming Technical Team 52