Gunther Verheyen

SEPTEMBER 16, 2022

Nor can there thus be much expectations (in a positive or negative sense) of the actual impact of my words or viewpoints regarding the question whether a process or framework (whatever name they chose for themselves) is “Agile”. Regarding the question whether a process or framework (whatever name they chose for themselves) is “Agile”.

Agile 78

Agile SCRUM 2013 Software Developers 78

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.” Scrum was instrumental in embracing software development as a form of new product development, and thus as complex work.

SCRUM 110

SCRUM 2003 2010 2013 110

MPUG

MAY 10, 2022

Scrum was originally used in software development projects. This made me an unsatisfied customer because I had no way to provide feedback throughout the process. Organizations may also choose to adopt various methodologies to begin managing in an Agile way.

Agile 59

Agile 2019 2013 Software Review 59

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. Daniels, Complex Adaptive Systems, Procedia Computer Science, 20 (2013), pp.

2014 45

2014 Aerospace 2011 2013 45

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. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp.

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. 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

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

Digite

MAY 15, 2018

Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Digite

JUNE 13, 2018

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. Make Process Policies Explicit.

Agile 110

Agile Technical Review Cadence Software Review 110

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. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

ProjectManager.com

MARCH 4, 2022

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology? Scrum Values.

SCRUM 337

SCRUM Software Review Development Team Review Underperforming Technical Team 337

Digite

JANUARY 2, 2017

Ken Schwaber has mentioned that SAFe does not adhere to the Agile Manifesto values (specially the first tenet – Individual and Interactions over Processes and Tool) as it is highly process-centric ( https://kenschwaber.wordpress.com/2013/08/06/unsafe-at-any-speed/ ).

Agile 60

Agile Cadence SCRUM 2013 60

Wrike

MAY 23, 2023

So we decided to consciously think about how to control this process, predict the potential problems of a rapidly growing test code base, and define the current problems and bottlenecks in the test development process, framework, and test infrastructure. A year later, in 2013, they succeeded again. Why “consciously?”

Engineering 36

Engineering Underperforming Technical Team Controlling Software Review 36

Herding Cats

AUGUST 25, 2017

Nature of the system to be developed - what's the basic processes of the system? Can All This Formality Have Any Use in Modern Software Development? Developing a Stakeholder-Assisted Agile CONOPS Development Process," Ali Mostashari, Sara A. Market considerations - who's going to buy this?

2014 38

2014 2013 2012 Engineering 38

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. . Estimating Processes in Support of Economic Analysis.

2007 42

2007 2012 2006 2008 42

Project Management Hacks

AUGUST 4, 2016

In 2013 , the company delivered 1.5 Through many discussions with my husband – who works in software development – I discovered an interest in the technology field. I led an effort to develop a risk-based software development process. What was the most valuable professional development activity (e.g.

2013 28

2013 2003 Technical Review 2010 28

LiquidPlanner

NOVEMBER 2, 2017

Sigmon gives project managers a defined process to not only break bad news, but also improve communication over the long-term. Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. If you work in the software and product development space, you should bookmark this blog.

Technical Review 113

Technical Review 2018 Certification Underperforming Technical Team 113

Planio

JULY 9, 2020

If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you! With the open source community behind it, Redmine has also developed a reputation for stability.

2006 88

2006 2007 Closing Agile 88

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. This is easy to learn, and anyone can learn what a product backlog is and how a particular process works. But the qualities above are difficult to train, and very crucial for agile success.

2011 37

2011 Lean 2013 Agile 37

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. This uncertainty is modeled as a stochastic process of an inherently random physical model. Now To Risk Management.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JANUARY 22, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. With this paradigm we have logically connected project management processes with Control System processesIf the variances, created by uncertainty going outside the UCL and LCL.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

OCTOBER 16, 2018

PP&C lives in the domain of Project Management and Controls, which is a Technical Management Processes of ISO 15288. In ISO 15288 this is the role of the Risk Management Processes. The life-cycle processes of a project can be defined by ISO15288 as. The Project Planning Process is where project management is anchored.

Aerospace 41

Aerospace Engineering 2012 2014 41

Herding Cats

FEBRUARY 4, 2017

The Measures that are modeled in the Cone of Uncertainty are the Quantitative basis of a control process that establishes the goal for the performance measures. Again this is simple statistical process control, using feedback to take corrective actions to control future outcomes - feedforward. Resources. [1] Air Force. [4]

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Scrum.org

AUGUST 17, 2020

Survival bias happens when failures are ignored when you are evaluating if a process or decision is the right one (Schermer, 2014). HR departments can conclude that their recruitment process is working well because it is producing suitable candidates. How many candidates did the process miss that would’ve been more suitable?

2015 219

2015 2014 2004 Influencer 219

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 165

Underperforming Technical Team 2007 2006 2009 165

International Institute for Learning

JULY 28, 2022

These are process driven organizations. They are more adaptive to changes , and besides being process driven , they are also product focused. In this article, I am not looking at Scrum from a software development perspective but rather from an organization-wide and project management perspective. PMP is very different.

Prince2 82

Prince2 SCRUM 2001 Agile 82

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

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

Herding Cats

OCTOBER 20, 2017

For software development systems like Kanban, which is production line-centric, Litle's Law tells us. λ = average production rate of complete software components. λ = average production rate of complete software components. There are two fundamental assumptions for Little's Law to work in the software development domain".

Underperforming Technical Team 34

Underperforming Technical Team 2008 Software Developers Software Development 34

Herding Cats

SEPTEMBER 27, 2016

The presentation " Quantifying the Impact of Agile Practices ," Larry MacCherone at the RallyOn 2013 Conference, presents some results on estimating impacts. The Software Development Performance Index (SDPI) scale on the left ranges - by eyeball measurement - from 46 to 55. How to Estimate Software Development.

Estimate 28

Estimate Agile 2013 Software Developers 28

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

APRIL 4, 2019

Lechler, Ting Gao, and Barbara Edington, Project Management Institute, 2013. Project Risk Management: Process, Techniques, and Insights , 2nd Edition, Chris Chapman and Stephen Ward, John Wiley & Sons, 2003. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996.

Risk Management 43

Risk Management Risk 2003 2011 43

Strategy Execution | PMO Perspectives

DECEMBER 13, 2018

It was not until about 2013 that Moonpig first began to adopt Agile practices. Moonpig began its agile transformation by establishing a Product Management team and cross-functional teams of developers and QAs. I spent many months getting to know the teams, what they did, their processes and their challenges and frustrations.

Agile 40

Agile Lean Engineering 2013 40

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

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. So individuals and interactions over processes and tools. And remember, agile is kind of born out of the need for technical project management or in many cases, software development.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40