Scrum.org

AUGUST 25, 2022

How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.

Sustainability 172

Sustainability 2015 2014 2013 172

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Wrike

NOVEMBER 7, 2018

Keys to Project Success: 48% say the team’s technical skills. 26% say effective team communication. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Poor visibility & resource management : 31%. Poor purchasing processes: 23%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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. Chakraborty and K.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. 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. 255, April 2010.

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

APRIL 16, 2019

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. Chartering the Team , Chartering empowers team members, both individuals and collectively. Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42