Gunther Verheyen

APRIL 24, 2020

Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.” In 2010 he initiated the creation of the Scrum Guide. Upon Jeff Sutherland’s consent, the Scrum Guide became the definitive body of knowledge holding the definition of Scrum (and what is not Scrum).

SCRUM 110

SCRUM 2003 2010 2013 110

Scrum.org

APRIL 7, 2022

Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime. Unfortunately, both the professional and the academic literature offer many different definitions. 40 years of storming: a historical review of Tuckman’s model of small group development.

Underperforming Technical Team 165

Underperforming Technical Team 2007 2006 2009 165

Digite

JANUARY 7, 2018

262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. David Anderson, who is widely regarded as the Kanban Method pioneer published this book in 2010.

Lean 79

Lean Software Review 2010 2014 79

MPUG

JANUARY 4, 2021

For at least twenty years and counting, the world around us has become more and more software driven, and, as a result, more digital. Electric vehicles are about 50% software, in terms of value, whereas fossil fuel cars are mostly hardware. Banks have essentially been software developing organizations for a long time.

Artificial Inteligence 122

Artificial Inteligence Critical Chain Underperforming Technical Team Agile 122

Herding Cats

OCTOBER 5, 2018

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

255, April 2010. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 24, 2010. “A Project Risk Management: Lessons Learned from Software Development Environment,” Y. 920, November 2004. Kwak and J. Yamamoto, and K.

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. 255, April 2010. 24, 2010. “A Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. First some definitions and a prior post on The Story Point Problem. References . [1]

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

DECEMBER 15, 2016

Laurens Eveleens and Chris Verhoef, IEEE Software , vol. 1, Jan-Feb 2010, pages 30-36. Forgetting even more that "agile" is a bottom-up software development solution. Chaos Report Myth Busters , . But here an alternative on how to report IT project success.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

JULY 24, 2017

It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. In all software development businesses, showing up late and over budget has a direct impact on the bottom line. . Thesis, George Mason University, 2010. "An

2007 42

2007 2012 2006 2008 42

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. David even built on the methodology to define the kanban method and released a book in 2010 called “Kanban: Successfully Evolutionary Change for your Technology Business”.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

NOVEMBER 5, 2018

In software development, those managing the project have some understanding the market forces (from their marketing departments), the technology (from their engineering department), and how to manage in the presence of Aleatory and Epistemic risk (the managers running a successful firm). Software development is a non-ergodic process.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

Herding Cats

APRIL 8, 2017

Much of the conversation in social media around agile techniques seems to be based on the differences between the variety of choices of a method, a process, or a practice and definitions of terms for those choices. 3] The Design History Reader, Grace Lees-Maffei (Editor), Rebecca Houze (Editor), Bloomsbury Academic, April 15, 2010.

Web Development 37

Web Development Software Engineering Engineering 2010 37

Herding Cats

MARCH 4, 2017

Before going let's look at the definition of the Cone of Uncertainty because it is misdefined and misused by some [4] in Wikipedia. Software development project schedule estimation has long been a difficult problem. Cone of Uncertainty definition (Wikipedia). Four sample causes are shown below. . References.

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

JANUARY 22, 2017

Here's a simple definition of the Cone of Uncertainty: . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?”

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Here's a simple definition of the Cone of Uncertainty: . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?”

Technical Review 28

Technical Review 2005 Estimate Software Review 28

MPUG

MAY 24, 2020

I’ve been working on creating blog posts and videos and giving speeches since 2010. So then if you do understand which questions are being asked by your team, you can get started creating some definitions behind the scenes. I do work for the North American market, I would say, but based in San Paolo.

Software Review 40

Software Review Artificial Inteligence Software Developers Software Development 40

Herding Cats

FEBRUARY 4, 2017

Here's a simple definition of the Cone of Uncertainty: . ASE’10, September 20–24, 2010, Antwerp, Belgium. . [8] Software Engineering Economics”. Software Sizing, Estimation, and Risk Management, Auer-bach, 2006. [15]Jorgensen, Software Development Effort Estimation: Formal Models or Expert Judgment?”

Technical Review 28

Technical Review Estimate 2005 Software Review 28

MPUG

SEPTEMBER 9, 2020

Satya N Dash: In addition to that, I have seen management practitioners when they create a plan, they make a lot of mistakes, without any software tool, in this case Microsoft Project. As early as 2009, 2010, nearly 11 years before I was working as a PMO. A good doctor will definitely have a perfect Start to Start. Kyle: Right.

Software Review 52

Software Review Critical Chain Technical Review Risk Management 52

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

OCTOBER 16, 2019

And that works doubly if you’re working in a software development environment is that, if you’re going to try and make Microsoft Project become your software developers tool, it’s not a right fit. That is great. And part of that is remember that this is a database, right?

Agile 40

Agile Technical Review Software Review Engineering 40