Scrum.org

NOVEMBER 15, 2018

Some years ago — in 2012 — I experienced my first Professional Scrum Master-class. Here was a trainer who was obviously not in it for the money, but was sincerely trying to improve the profession of software development. Although I had been teaching and training Scrum since 2012, it was never as a Professional Scrum Trainer.

SCRUM 97

SCRUM 2012 2018 Software Review 97

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. Accuracy - how close is the estimate to the actual value? Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. For our credible.

2003 46

2003 2014 2015 2011 46

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. Wallshein, Ph.D. Laird and M.

2007 42

2007 2012 2006 2008 42

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. Thesis, University of Southern California, August 2012.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Leading Agile

JUNE 27, 2018

” I was reminded of the old joke by a recent article by John Regehr, Professor of Computer Science at the University of Utah, entitled “Closing the Loop: The Importance of External Engagement in Computer Science Research.” In 2012, I wrote a blog post entitled “Delivering provably-correct code.”

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

Scrum.org

APRIL 7, 2022

Edmondson (2012) argues that dynamic teaming is important to share and encourage learning. This is also what inspired Edmondson (2012) in her academic work on “teaming”. They also tend to perform better (Evans & Dion, 2012), are better able to deal with stress and pressure (Salas, Driskell & Hughes, 1996). Bradley et.

Underperforming Technical Team 175

Underperforming Technical Team 2007 2006 2009 175

Leading Agile

JUNE 18, 2018

Defensive programming consists of learning and using guidelines for software design and coding that tend to minimize the frequency and severity of problems in production. The day came when the software community more-or-less forgot about defensive programming. I guess that worked out okay for a generation of developers.

Software Review 101

Software Review Underperforming Technical Team Technical Review Artificial Inteligence 101

Scrum.org

FEBRUARY 15, 2020

If we look at the Stacey Matrix adapted for software development, a complex domain is where there are more unknown variables that cannot be predicted and there is no definite path to reach the goal. In the movie Avengers (2012), The Mind Stone allows the user to control the minds of others and can control what they do.

SCRUM 182

SCRUM Development Team Review 2012 Technical Review 182

Scrum.org

AUGUST 17, 2020

The fallacy happens when we conclude from this that punishment works, and rewards don’t (Defulio, 2012). When comparing different approaches to develop software, survival bias can lead someone to conclude that plan-driven approaches work well based on a few success stories they have where they did. Closing words.

2015 225

2015 2014 2004 Influencer 225

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