Scrum.org

NOVEMBER 29, 2022

Sadly, there is a knowledge gap in assisting organisations in understanding strategies that can influence their agility and support teams in change. Venkatesh Rajamani has more than 18 years of experience delivering working software in short, feedback-driven cycles. 2019, December 2). 2019, December 2). References.

Telecoms 159

Telecoms 2019 2018 Software Engineering 159

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Unger-Windeler and her colleagues (2019) also investigated what Product Owners do in many different organizations and concluded that “no Product Owner role is like another”. This post is part of our “in-depth” series.

2014 208

2014 2008 Technical Review 2019 208

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Turof, IOP Conference Series: Materials Science and Engineering , 400, 2018. “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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Springer, Singapore, 2019.

Estimate 40

Estimate Software Review Software 2012 40