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 ). My work as an independent Scrum Caretaker via my one-person company Ullizee-Inc is the sole source of money for our family. Scrum is what I do for a living. Let there be no misunderstanding: money is important.

2001 67

2001 2013 2024 SCRUM 67

Gunther Verheyen

MAY 3, 2021

The updated, third edition of my book “Scrum – A Pocket Guide” is now available worldwide, as a digital and as a paperback edition. I accidentally created the first edition of my book “Scrum – A Pocket Guide” in 2013. I consider how I described the Scrum Values in that first edition.

SCRUM 98

SCRUM 2013 2020 2016 98

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders. The Scrum Guide seems pretty clear about what Product Owners are accountable for.

2014 216

2014 2008 Technical Review 2019 216

Scrum.org

NOVEMBER 6, 2018

"There's no predictability/commitment in Agile/Scrum". They are either already victims of "Bad Scrum" or are basing their concerns off of a lot of "Bad Scrum" going on out there. Why didn't I just say "Agile/Scrum provides great predictability" and get it over with? See Chaos Report 2013 ). .

Underperforming Technical Team 129

Underperforming Technical Team Risk SCRUM Executing 129

Digite

MAY 15, 2018

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Binfire

NOVEMBER 29, 2022

This company is a dinosaur in blockchain terms because it’s been around since 2013, meaning they know how things work. Jira was designed with software developers in mind, but you can use the app no matter what industry you’re in. Both scrum tactics and kanban boards can be integrated with Jira, which makes it highly versatile.

2013 78

2013 Software Developers Software Development SCRUM 78

International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). 2009), include eXtreme Programming (XP) (Beck and Fowler, 2001) and Scrum (Schwaber and Beedle, 2002).

Innovation 59

Innovation Agile 2002 2001 59

Gunther Verheyen

DECEMBER 19, 2018

In 2013 I accidentally created a book, “Scrum – A Pocket Guide” In 2018 I deliberately evolved my Scrum travel companion into a second edition. I am humbled over the many unanticipated consequences of the accidental creation of my pocket guide to Scrum. In July 2016 they were added to the Scrum Guide.

SCRUM 77

SCRUM 2013 2016 2017 77

Scrum.org

AUGUST 25, 2022

It is very similar to work engagement (Schaufeli & Salanova, 2014), which we also measure in both the Scrum Team Survey and TeamMetrics (as “team morale”). al, 2013), healthcare professionals (Papathanasiou et. 2013), and in the workplace (Manganelli, Thibault-Landry & Forest, 2018). In Achieving Quality in Software (pp.

Sustainability 183

Sustainability 2015 2014 2013 183

Gunther Verheyen

SEPTEMBER 16, 2022

Agile nor Scrum. Judging by the number of people actually actively joining me in my journey of humanizing the workplace with Scrum(extremely low), much of the expressed ‘respect’ is no more than paying lip service. There are already so many haters and bashers, certainly regarding my favourite tool, Scrum.

Agile 78

Agile SCRUM 2013 Software Developers 78

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. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition. Scrum Values.

SCRUM 338

SCRUM Software Review Development Team Review Underperforming Technical Team 338

MPUG

MAY 10, 2022

For example, Scrum is a methodology which emphasizes delivery in short increments and frequent meetings. Scrum was originally used in software development projects. There are always unknown factors in a project, but in the Agile approach, you regularly meet to address those factors and plan an approach for moving forward.

Agile 59

Agile 2019 2013 Software Review 59

Digite

JANUARY 2, 2017

Since the arrival of Scaled Agile Framework in the world market, there have been comparisons ad nauseum between the Scrum and SAFe frameworks. Those who have undergone any initiation to SAFe would confirm that at Team level, SAFe works very much like standard Scrum, although the teams can also work in Kanban.

Agile 60

Agile Cadence SCRUM 2013 60

Herding Cats

MAY 10, 2019

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. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46

2003 2014 2015 2011 46

Digite

JUNE 13, 2018

Compared to Scrum, Kanban is a young work-management method. 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.

Agile 110

Agile Technical Review Cadence Software Review 110

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. Dorofee, et.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Scrum.org

JUNE 17, 2019

Scrum cumplió 21 años en 2016. Desde 2011 ha habido dos grandes cambios en la guía de Scrum , en 2013 y 2016. Se reforzó el énfasis en el Daily Scrum como elemento de planificación -y no solamente sincronización- y también se cambió el nombre de la reunión de grooming a refinenement. Con muchos cambios.

SCRUM 20

SCRUM 2011 2016 2013 20

LiquidPlanner

NOVEMBER 2, 2017

Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. We recommend checking out the “Project Management Training Bundle”, which gives you access to the PM certification courses, as well as the Agile and scrum certification courses. Scrum Certifications. Cost: $6,570.

Technical Review 113

Technical Review 2018 Certification Underperforming Technical Team 113

Planio

JULY 9, 2020

Even software. Comfort knowing you’re always running the latest, most stable version of the software. 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!

2006 88

2006 2007 Closing Agile 88

Project Pulse Journal

MARCH 11, 2024

Examples of a very well-established and "operationalized" way of project management are ticket tracking in project management software and the Scrum Framework that provides insights on how to communicate better, send feedback, and collaborate across the different teams and entities involved in project delivery. Alderton, M.

Innovation 52

Innovation Sustainability Monitoring Risk Management 52

Scrum.org

SEPTEMBER 11, 2020

Everybody wants to Scale Scrum. So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way. This is more or less the time you started searching for "scaling agile" "scaling scrum" and exploring your options.

SCRUM 204

SCRUM 2008 2013 Software Review 204

International Institute for Learning

JULY 28, 2022

I hear people often talk about Scrum projects, but what does Scrum have to do with project management? In this article, I am not looking at Scrum from a software development perspective but rather from an organization-wide and project management perspective. In Scrum , we have three roles.

Prince2 82

Prince2 SCRUM 2001 Agile 82

nTask

AUGUST 22, 2019

“Scrum” is a phenomenal subject – i.e. if you are familiar with it. As an Agile project manager, I have seen my fair share of so-called “Scrum Masters” and “Agile Experts” claiming to be masters of their craft. The truth, however, is that they don’t know a lot of things about Scrum and Agile. Introduction – Why Scrum?

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

Scrum.org

JUNE 24, 2019

En ocasiones se convierte en un arma arromadiza que los stakeholders, el Product Owner o incluso el Scrum Master utilizan para controlar el equipo. ¿Es Aunque los Stakeholders , el Product Owner o el Scrum Master puedan ver el Sprint Backlog, éste es propiedad del Equipo de Desarrollo. Es esta su función? Qué es el Sprint Backlog.

2013 25

2013 SCRUM Planning Software 25

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.” - K. Schwaber and J.

Underperforming Technical Team 239

Underperforming Technical Team Technical Review Software Review Development Team Review 239

Rebel’s Guide to PM

OCTOBER 28, 2022

A survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Technical Review 395

Technical Review Software Review 2013 Software 395

Scrum.org

AUGUST 17, 2020

See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.

2015 221

2015 2014 2004 Influencer 221

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Governance 52

Governance Government Software Review Software 52

MPUG

JULY 30, 2020

Please find below a transcription of the audio portion of Rich Murphy’s showcase session, Triskell Software for Enterprise Governance, being provided by MPUG for the convenience of our members. Kyle: Hello everyone, and welcome to today’s MPUG vendor showcase session, Triskell Software for Enterprise Governance.

Governance 52

Governance Government Software Review Software 52

Scrum.org

DECEMBER 23, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why do software teams?—?despite 2013) actually suggests that code smells themselves are not necessarily the issue, but the length of the class being edited and the number of changes made to it over time.

Software Review 183

Software Review Technical Review Underperforming Technical Team 2015 183

Scrum.org

APRIL 7, 2022

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. Information and Software Technology , 48 (4), 235–244. Bradley et.

Underperforming Technical Team 168

Underperforming Technical Team 2007 2006 2009 168

Agilemania

APRIL 20, 2021

Large-Scale Scrum (LeSS): Craig Larman and Bas Vodde created the LeSS framework. It developed by taking Scrum and trying many different experiments to discover what works. In 2013, the experiments were solidified into the LeSS framework rules. It is a framework build upon Scrum but keeps Scrum untouched.

Agile 93

Agile Telecoms 2011 2013 93

Rebel’s Guide to PM

JUNE 24, 2019

A 2017 survey showed that teams using Slack had: 32% less email 23% fewer meetings 24% of features (in technical teams) delivered on time 27% less time required for software testing 10% improvement in employee satisfaction. For most projects, you are going to need something else as well to create your Gantt chart or Scrum board, for example.

Software Review 219

Software Review Technical Review 2013 2017 219

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. Most Popular Agile Tools and Processes: Scrum – 43%. Project Management Software & Tools. 77% of companies use project management software, and 87% of high-performing companies use project management software. [5]. Most-Wanted Features in Project Management Software: 1.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Agilemania

APRIL 20, 2021

Large-Scale Scrum (LeSS): Craig Larman and Bas Vodde created the LeSS framework. It developed by taking Scrum and trying many different experiments to discover what works. In 2013, the experiments were solidified into the LeSS framework rules. It is a framework build upon Scrum but keeps Scrum untouched.

Agile 52

Agile Telecoms 2011 2013 52

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40