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. Why our brain is not built for software engineering. Cognitive paradigms, applied to Scrum / Agile.

2002 190

2002 SCRUM 2007 2003 190

Project Pulse Journal

APRIL 15, 2024

Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Beyond Scrum , several Agile frameworks were developed to address the unique needs and challenges of projects and teams.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Herding Cats

MAY 10, 2019

Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. 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. 105, 2003. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Effective Risk Management 2nd Edition, Edmund Conrow, AIAA, 2003. A Taxonomy-based Model for Identifying Risks, Sebastian Maniasi, Paola Veronica Britos, and Ramon Garcia-Mertinez, JIISIC'06 - V Jornadas Iberoamericanas de Ingeniería de Software e Ingeniería del Conocimiento, Memoria Técnica, Proceedings, Puebla, Pue. 105, 2003. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MAY 7, 2019

Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 21 September 2012.

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. . 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. 5 Oct 1990, Page 21.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

JANUARY 23, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Hire someone who does.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37