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 214

Agile 2010 2013 2008 214

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 79, 2008. “`,” Stephen Ward and Chris Chapman , International Journal of Project Management , 21, pp. Software Engineering Institute, January 1996. 255, April 2010. Raz and E. “A

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. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

NOVEMBER 12, 2016

The paper Agile Base Patterns in the Agile Canon , Daniel R Greening, 2016 49th Hawaii International Conference on System Sciences is an important contribution to the discussion of agile at scale in organizations beyond 5 developers at the table with their customer. The Agile Cannon is composed of 5 elements. Understanding.

Agile 61

Agile 2009 2008 2011 61

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. 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: 2008 (revised edition). Published date: 2016. Project Management for Humans: Helping People Get Things Done.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148