Scrum.org

JANUARY 13, 2019

While our industry has talked about poker planning and story points since almost the beginning of agility in 2001, I think it is more than time that the conversation at sprint planning shifts to historical throughput instead of using velocity.

2001 98

2001 Software Engineering SCRUM Engineering 98

Gunther Verheyen

DECEMBER 26, 2023

We have three kids (2001, 2003, 2013) of which the two oldest (sons) have a disability ( Duchenne and Down Syndrome ). Money was not what drove my wife and I when I gave up my position as software engineer and aspiring project manager in favor of running a bookshop (1996). Let there be no misunderstanding: money is important.

2001 67

2001 2013 2024 SCRUM 67

Scrum.org

OCTOBER 19, 2022

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So SCRUM and productivity in software projects: a systematic literature review. In 14th International Conference on Evaluation and Assessment in Software Engineering (EASE) (pp. A survey study of critical success factors in agile software projects.

Agile 204

Agile 2010 2013 2008 204

Herding Cats

NOVEMBER 7, 2016

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. Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 7, 2019

Bool, CrossLink: The Aerospace Corporation, Winter, 2000/2001, pp. 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. Estimating Probable System Cost,” Stephen A.

Estimate 40

Estimate Software Review Software 2012 40

Scrum.org

FEBRUARY 3, 2020

The article discusses possible scientific explanations for the success of a personal productivity approach called “ Getting Things Done ” (GTD; Allen, 2001). Why our brain is not built for software engineering. 2001): Cybernetics and Second Order Cybernetics, in: R.A. Lutterbeck, M. Bärwolff & R. Gehring (eds.),

2002 197

2002 SCRUM 2007 2003 197

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Binfire

AUGUST 28, 2019

The 12 rules of Agile project management principles are based on the Agile manifesto published by the Agile working group in February 2001. Please customers through early and continuous software delivery. Agile was written by software engineers for software engineers, but over the years it has proven its value in other disciplines.

Agile 60

Agile Technical Review Sustainability Software Review 60

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. Pich, Christoph H.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Agilemania

MARCH 3, 2022

The Development Team includes professionals like software developers, architects, programmers, analysts, system admins, QA experts, testers, UI designers, etc. It is a non-profit organization founded in 2001. Software Engineers . Brief about Scrum Alliance. It has served 1, 082, 451 certificates till date. .

Certification 52

Certification Lean Development Team Review Engineering 52

Project Pulse Journal

APRIL 15, 2024

Transitioning from manufacturing to software engineering and development and various other industries, the Kanban Board has become a fundamental tool for visual management in project and workflow management, credited to the Agile movement. 2001, December). References Kanban Tool by Shore Labs. History of Kanban. ComputerWorld.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Herding Cats

OCTOBER 24, 2018

“Automated Root Cause Isolation of Performance Regressions during Software Development,” Christopher Heger, Jens Happer, and Roozbeh Farahbod, ICPE ’13, April 21?24, Agile process Smell and Root Cause Analysis,” Dave Nicolette, International Conference on Agile Processes and Extreme Programing in Software Engineering, 2009.

2014 45

2014 Aerospace 2011 2013 45

Leading Agile

JUNE 20, 2018

The idea of a self-organizing team has been promoted strongly since the Agile movement started to gain popularity following the publication of the Agile Manifesto in 2001. I can imagine some software engineers taking umbrage at that comment. After all, they are so smart that they can figure out anything, right?

Agile 94

Agile Defining 2001 2009 94

Binfire

APRIL 7, 2017

In the late twenty century many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100