Scrum.org

MAY 26, 2020

Christiaan and Barry are both Professional Scrum Trainers (PST) with Scrum.org, dedicated early adopters of Liberating Structures, and co-authors of the upcoming Zombie Scrum Survival Guide. Both are Professional Scrum Trainers and Liberating Structures enthusiasts. Also, they are co-authors of the upcoming Zombie Scrum book .

Agile 100

Agile 2004 SCRUM Software Developers 100

Scrum.org

AUGUST 22, 2019

Early September a new book will be added to the Professional Scrum Series : Agile Leadership Toolkit - by Peter Koning. We live in uncertain times created by the move from the age of mass production to the digital or software age. Scrum, Less, and other agile methodologies promise motived, collaborative, and highperforming teams.

Leadership 92

Leadership Agile 2004 Underperforming Technical Team 92

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. 920, November 2004. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. Q1: Is Kanban better than scrum? The Scrum board is more methodical. Who Uses Kanban?

Software Review 81

Software Review Technical Review 2004 SCRUM 81

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

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

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. Cognitive paradigms, applied to Scrum / Agile.

2002 203

2002 SCRUM 2007 2003 203

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46

2003 2014 2015 2011 46

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 222

2015 2014 2004 Influencer 222

Scrum.org

JANUARY 27, 2021

Audience: Scrum Masters , Leaders. As the world became more complicated, we created automation using machinery with software to control it. This was the birth of the Agile movement with the Scrum Framework (1993), the Agile Manifesto (2001), and later Kanban (2004). Read: The Scrum Guide. The Scrum Guide.

2001 214

2001 Software Review Technical Review Underperforming Technical Team 214

MPUG

DECEMBER 3, 2021

He joined Edwards in 2004 as a project coordinator and scheduler and provided project planning and scheduling support to variety of commercial and federal government clients. Walter Stinnett: For example, software implementation project for a system you’re not familiar. Walter’s certifications include the PMP and MCTS.

Software Review 52

Software Review Technical Review Underperforming Technical Team Risk Management 52

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

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

Estimate 40

Estimate Software Review Software 2012 40

Leading Agile

MARCH 11, 2020

What was that, probably 2004, or ’05 or something in that kind of range, I think? And in those days, so if this was 2004, 2005, something in that kind of range, in those days, then, you know, for the most part, Agile was still maybe one team of six, or eight, or 10. – Sure, sure. – [Brian] Yeah, something like that.

Agile 103

Agile Fractional CTO CTO Hire Influencer 103

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell.

Estimate 64

Estimate 2006 2005 2013 64