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). Analysis of fault generation caused by stress during software development.

2004 230

2004 2010 2009 2016 230

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

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Deliverables Based Planning: Providing Actional Information to the Program Manager - 11th Annual Rocky Mountain Project Management Symposium , 2009. Dallas MPUG , May 6th, 2009.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

JUNE 20, 2018

But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development. Neither are they free from influence.” In 2013 I described a conference session Pelrine facilitated in which we explored this concept in 2009.

Agile 94

Agile Defining 2001 2009 94