Gunther Verheyen

DECEMBER 17, 2020

The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? How did its definition evolve before and after 2010 and become the framework that we know today? The Scrum Guide holds the definition of Scrum, they say.

2010 141

2010 SCRUM 2002 2004 141

Scrum.org

APRIL 7, 2022

As we will see below, current scientific models for team formation underscore the need for time and frequent interaction to allow teams to develop the tissue that makes them high-performing. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner.

Underperforming Technical Team 176

Underperforming Technical Team 2007 2006 2009 176

Herding Cats

MARCH 11, 2018

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. ISO 31000:2009, ISO 17666:2016, and ISO 11231:2010 Risk is Uncertainty that Matters. Now To Risk Management.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Digite

JANUARY 7, 2018

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. 262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). Successful Evolutionary Change for Your Technology Business.

Lean 79

Lean Software Review 2010 2014 79

Gunther Verheyen

APRIL 24, 2020

Jeff Sutherland and Ken Schwaber moved the development of Scrum forward in the early 1990s. Ken Schwaber first documented Scrum in 1995 in the paper “ SCRUM Development Process.” In 2010 he initiated the creation of the Scrum Guide. They are the co-creators and gatekeepers of (what is) Scrum.

SCRUM 110

SCRUM 2003 2010 2013 110

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. The Future of Systems-and Software Development.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MARCH 17, 2019

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Product & Process Development Kaizen , LPPDE, Denver, Colorado, April 21-23, 2008.

2003 54

2003 2011 2008 Performance Measurement 54

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 ? The program management processes should seek to reduce uncertainty in the variable of the project. Steve McConnell. 37–48, 2007.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. 255, April 2010. 24, 2010. “A Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Scrum.org

MAY 26, 2020

Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. I was responsible for managing software development projects. Developers, because of the growing crunch-culture. This wasn’t a success. Everyone was unhappy. So the toolbox is diverse.

Agile 102

Agile 2004 SCRUM Software Developers 102

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

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

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

nTask

NOVEMBER 23, 2018

Introduced in 2006, with a major redesign in 2010, the platform serves as a single systematic and flexible solution for all the task management needs of a team. A versatile project management software equipped with an intelligent toolset that caters perfectly to all individual as well as team task management needs. Key Features.

2019 111

2019 2006 2010 Software Review 111

Wrike

NOVEMBER 7, 2018

Having a knowledge transfer process in place boosts the chance of project success by over 20%. [6]. Most Popular Agile Tools and Processes: Scrum – 43%. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Poor purchasing processes: 23%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Project Pulse Journal

MARCH 25, 2024

The development process of products and the project lifecycle integrate to deliver the perceived value to stakeholders. Product Life Cycle Management Managing the life cycle of products from planning and development to launch and sustainment is vital for adapting to evolving customer expectations and technological advancements.

Sustainability 52

Sustainability Innovation Development Team Review 2024 52

Wrike

MAY 23, 2023

I joined the team as a QAA engineer in 2010, the first employee in this role. Together, we have developed a unique quality control system for Wrike, our lovely project management platform, allowing us to deploy product code to production more quickly and without bugs. Hello, everyone! I’m Alexander, and I’m a QAA manager at Wrike.

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Herding Cats

AUGUST 1, 2018

Specific actions to reduce the Episuncertaintiesnaties and Margin to handle the Aleatory uncertainies are part of any good project management process. . The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

nTask

AUGUST 8, 2019

We have gone an extra mile to illustrate various real life use cases and examples where waterfall is implemented, and how one can use nTask to further simplify that process – so on and so forth. It follows a sequential, linear process which is why it is often described as a “linear-sequential life cycle model”.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Scrum.org

JUNE 5, 2019

Why is there such a strong emphasis on the people needed for the process and so little on the people doing the work? Agile software development started with developers. These days, it seems to be more about Scrum Masters, Agile Coaches, Product Owners, and other “process roles”. the “process people”?—?as

SCRUM 142

SCRUM 2002 2003 2001 142

ProProfs Project Management

JANUARY 15, 2021

Here’s how the project kanban board looks like: Kanban technique originated from Toyota’s “just-in-time” (JIT) production system and created by Taiichi Ohno who wanted a simple planning system in place to help them manage and control the production process efficiently. Coordinating Sales Process. However, after 1940 David J.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

Herding Cats

APRIL 4, 2019

Misconceptions of Risk , Terje Aven, John Wiley & Sons, 2010. Critical Code, Software Producibility for Defense, Committee for Advancing Software-Intensive Systems Producibility , Computer Science and Telecommunications Board Division on Engineering and Physical Sciences, National Research Council of the National Academies, 2010.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Herding Cats

NOVEMBER 14, 2018

This method is the Analytic Hierarchy Process (AHP). 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. The Wrap Up . References . [1]

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Digite

MARCH 12, 2018

In the usual Scrum process, the P.O. I have often wondered – doesn’t speak too well of us as software professionals! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. Also, we have quite diverse roles in the team (i.e., Our Kanban Journey.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Herding Cats

JANUARY 9, 2017

Aleatory uncertainty, which is the naturally occurring yields variances in the underlying processes. Epistemic uncertainty comes from probabilistic processes that can be addressed with handling responses. The idea of risk and its management and handling is a critical success factor for all software development.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

SEPTEMBER 19, 2018

The business as usual, but with some technical processes get a bit wider. Flight software is always an issue where we work, so those ranges are wider even more. The Triangle distribution is a good place to start since it models the log-normal distribution which is found for many naturally occurring processes.

Technical Review 43

Technical Review 2010 Estimate Software Review 43

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 , . Willian pointed out the bands for measuring success. Related articles.

2006 28

2006 2010 Estimate Agile 28

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

Software 38

Software 2006 Software Developers Software Development 38

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 projects are non-ergodic.

Software Review 34

Software Review Technical Review Estimate Software Developers 34

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

Herding Cats

APRIL 16, 2019

Management Processes (#MP). Agile Software Development (#ASD). While many of the presentations have similar titles, the content is focused on a specific set of processes and practices, while the principles are the same, since they are Immutable. . Management Processes. Project Performance Management (#PPM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Wrike

AUGUST 14, 2020

Toyota was looking for a way to improve their engineering and production processes. The Kanban process was the result of this adaptation. . Toyota used physical cards to signal separate steps in their manufacturing process. Anderson is often credited as being the first to implement Kanban in software development in 2005.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

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. Other work in website development, others work in internal IT shops. Two Books in the Spectrum of Software Development.

Web Development 37

Web Development Software Engineering Engineering 2010 37

Herding Cats

MARCH 4, 2017

The uncertainty is always there, it doesn't go away with specific actions in specific domains, or with the use of any tools, processes, or practices. If they are not reducing, then the project is headed for trouble, the and management processes of the project has failed to performance its job. . For example for a recent paper abstract.

2010 28

2010 2007 Estimate Aerospace 28

EasyProjects

SEPTEMBER 24, 2019

Have you ever seen a chef send a dish out without tasting it several times at every stage of the process? According to the Project Management Institute, agile processes initially slow a team down because of the learning curve. Scrum is used by software development teams. Disgusting. Well, you kinda deserved that.

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41