Scrum.org

AUGUST 1, 2022

Butchibabu and her colleagues (2016) performed an experiment with 13 teams. Many studies have found that psychological safety has a positive influence on team effectiveness (Edmondson, 2014). We wrote a lot more about stress and sustainable pace in this post , as well as examples of work agreements. References. Butchibabu, A.,

2004 228

2004 2010 2009 2016 228

Scrum.org

OCTOBER 19, 2022

Several empirical studies have indeed found that teams with a frequent delivery strategy are more likely to deliver successful project outcomes and satisfy stakeholders than teams that do not ( Chow & Cao, 2008 , Jørgensen, 2016 ). 2014 ; Young & Jordan, 2008 ; Russo, 2021 ). Information and Software Technology , 78 , 83–94.

Agile 205

Agile 2010 2013 2008 205

Herding Cats

MAY 10, 2019

“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. 1, March 2014. Dorofee, et.

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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. This process starts with the Concept of Operation, IPM 2016 , October 31 - November 2, 2016. . College of Performance Management , IPM Workshop, 2016. Balanced Scorecard (#BSC).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Planio

JULY 22, 2020

If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Published date: 2014. Published date: 2014. Published date: 2016. Author: Brett Harned. Published date: 2017.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148