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. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp.

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. 920, November 2004. 255, April 2010.

Risk Management 35

Risk Management Risk Technical Review 2002 35

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. So much that it is being used for other projects besides software development. To become agile, it is important to implement the feedback loops. Happy reading!

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Gunther Verheyen

FEBRUARY 27, 2024

In the summer of 2019 I got in touch with O’Reilly Media about their ambition to add a book about Scrum to their “97 Things” series. For that reason I did not want any specific Scrum accountability in the title.

SCRUM 71

SCRUM 2004 Software Review 2019 71

Herding Cats

MARCH 11, 2017

This is the motivation for short work intervals found in agile development. . Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO. The probability of something happening.

2003 46

2003 2014 2015 2011 46

Scrum.org

FEBRUARY 3, 2020

Their paper provides useful insights into why the Scrum Framework might be so effective when it comes to managing complex work. Their article inspired me to apply the same insights to Scrum and to extend it with my own. Software development is (generally speaking) very complex. waterfalls) are very likely to fail.

2002 202

2002 SCRUM 2007 2003 202

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 220

2015 2014 2004 Influencer 220

Scrum.org

JANUARY 27, 2021

Audience: Scrum Masters , Leaders. In the complex world of Sales, Marketing, and Software Development, we also needed new ways of thinking that would power the same ideas from Toyota and Lean into the high variance world of complex cognitive work. Agile Manifesto, 2001. Read: The Scrum Guide. The Scrum Guide.

2001 211

2001 Software Review Technical Review Underperforming Technical Team 211

Herding Cats

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Effective Opportunity Management for Project: Exploiting Positive Risk , David Hillson, Taylor & Francis, 2004.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). Those lessons are directly transferable to the management of software development teams.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

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). 449-462, July 2004.

Estimate 64

Estimate 2006 2005 2013 64