Scrum.org

AUGUST 1, 2022

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). This ties closely into research on team cognition and cross-functionality.

2004 225

2004 2010 2009 2016 225

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. Software Engineering Institute, January 1996. Project Risk Management: Lessons Learned from Software Development Environment,” Y. 532, August 2009.

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. 5887, 2009. Risk a Feelings,” George F.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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

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. Dallas MPUG , May 6th, 2009. Strategy (#Strategy).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

NOVEMBER 17, 2020

So we first worked together, I guess it was probably back in like late 2009, 2010. But if you’re not doing it with like executive support and with an integrated strategy from beginning to end, it’s really difficult to sustain momentum. So— – We reconnected, yeah. I had joined Pillar for a little bit.

Technical Review 86

Technical Review Software Review Agile Governance 86