Gunther Verheyen

DECEMBER 17, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996) The paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 141

2010 SCRUM 2002 2004 141

Scrum.org

AUGUST 25, 2022

It is also the reason why the principles of the Agile Manifesto can create such motivating environments. al, 2013), healthcare professionals (Papathanasiou et. 2013), and in the workplace (Manganelli, Thibault-Landry & Forest, 2018). Analysis of fault generation caused by stress during software development.

Sustainability 172

Sustainability 2015 2014 2013 172

Digite

JUNE 13, 2018

We’re honored to republish this blog post ‘Beginner’s Guide to Kanban for Agile Marketing’ by Andrea Fryrear which was originally published in the Agile Sherpas blog! Once you’re confident that the flow reflects your team’s flow, you can create a more permanent version with tape or software.

Agile 110

Agile Technical Review Cadence Software Review 110

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. Many industry experts have come out and pointed possible flaws in the Scaled Agile Framework. However, the Scaled Agile Framework indeed subscribes to the ethos of the Agile manifesto.

Agile 60

Agile Cadence SCRUM 2013 60

Gunther Verheyen

APRIL 24, 2020

Having worked with Scrum since 2003, I am fascinated by its ever-expanding use, which is not limited to software and (new) product development. Jeff Sutherland and Ken Schwaber moved the development of Scrum forward in the early 1990s. These six essential traits are indicative of Scrum coming to life. Gunther Verheyen.

SCRUM 110

SCRUM 2003 2010 2013 110

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.

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 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Agile Project Management. A paradigm of Agile Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

Teamweek

JUNE 17, 2020

This new approach puts the focus on adaptability or agility. Agility refers to “an organization’s ability to alter its direction or adjust to operate successfully,” according to leadership consultant Ryan Gottfredson. The terminology is borrowed from software developers. The Project-Based Career Ladder.

Technical Review 90

Technical Review 2013 Consulting Innovation 90

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. This is the motivation for short work intervals found in agile development. . Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Digite

MAY 15, 2018

It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. As I wrote in 2013, Scrum and Kanban both share a use of values to encourage users of the methods to behave a certain way. You should go read it now.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

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. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

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. More and different people look for guidance and insights on their journey of Scrum, increasingly in domains beyond software development.

SCRUM 77

SCRUM 2013 2016 2017 77

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. Learn More!

SCRUM 332

SCRUM Software Review Development Team Review Underperforming Technical Team 332

Gunther Verheyen

FEBRUARY 26, 2024

I embarked on my Agile journey in 2003 when we wrapped eXtreme Programming in Scrum. From 2013-2016 I maintained the official “Professional Scrum” series of Scrum.org meanwhile training candidate-PSTs and shepherding the global community of Professional Scrum Trainers and coaches.

SCRUM 74

SCRUM Certification 2016 2011 74

Planio

JULY 9, 2020

Even software. Comfort knowing you’re always running the latest, most stable version of the software. Agile Project Management out of the box. Not only does this mean that Redmine will stay compatible with the latest hardware and software, but also that the product itself will most likely never go away. What is Redmine?

2006 88

2006 2007 Closing Agile 88

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. And if the competitor is shipping software with greater value, how does the Cone impact that? 37-48, 2007. 37-48, 2007. Thesis, University of Southern California, August 2012.

2007 34

2007 2012 2009 2010 34

LiquidPlanner

NOVEMBER 2, 2017

He explains how to succeed or fail fast for projects that are too uncertain to use waterfall project management and too complex to succeed with agile project management. Hosted by Peter Taylor, this podcast began in 2013 after he published his best-selling book by the same name. Cost: Coursera: Agile Development Specialization.

Technical Review 113

Technical Review 2018 Certification Underperforming Technical Team 113

Herding Cats

AUGUST 25, 2017

Can All This Formality Have Any Use in Modern Software Development? The notion that agile development is a free-for-all development of what ever the customer wants to produce next, with the customer identifying the next important thing to develop works just fine for de minimus projects. McComb, Deanna M.

2014 38

2014 2013 2012 Engineering 38

Stepping Into Project Management

MARCH 10, 2014

Today we interview Siddhartha Govindraj, who specializes in Lean/Agile processes for software development. An occasional organizer of events as a part of Chennai Agile User Group and speaks in conferences in India and abroad. Agile becoming mainstream now, how do you think the world of project management has changed?

2011 37

2011 Lean 2013 Agile 37

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

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Eng.,

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. 2] System Analysis, Design, and Development Concepts, Principles, and Practices, Charles Wasson, John Wiley & Sons. [3] 4] Defense Acquisition Guide , Chapter 4, Systems Engineering , 15 May 2013. [5] Software Engineering Economics”. Software Eng.,

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. There could be many reasons why - perhaps your organization has adopted an Agile framework, but you're not yet structured to support sustainable teams. You may have a strong reliance on vendors or specialists when you start your Agile journey. Schwaber and J.

Underperforming Technical Team 231

Underperforming Technical Team Technical Review Software Review Development Team Review 231

MPUG

OCTOBER 9, 2019

Please find below a transcription of the audio portion of Tim Runcie’s Agile Series Part 1 webinar being provided by MPUG for the convenience of our members. Kyle: Hello everyone and welcome to today’s MPUG training series, part one, Understanding and Incorporating Agile Project Management. It’s not all or nothing.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

International Institute for Learning

JULY 28, 2022

Scrum has its origins in software development, but about ten years ago, other departments in organizations started looking at becoming more agile and analyzing whether the Scrum approach could also be used in their departments— and in projects. The latest version is more agile compatible. Peter Krischel.

Prince2 82

Prince2 SCRUM 2001 Agile 82

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. This corresponds with research on autonomous teams, as well as principles of Agile software development.

Underperforming Technical Team 157

Underperforming Technical Team 2007 2006 2009 157

Scrum.org

AUGUST 17, 2020

When comparing different approaches to develop software, survival bias can lead someone to conclude that plan-driven approaches work well based on a few success stories they have where they did. All drivers consider their own driving skills above average (Roy & Liersch, 2013). The intuitive psychologist and his shortcomings.

2015 213

2015 2014 2004 Influencer 213

Strategy Execution | PMO Perspectives

DECEMBER 13, 2018

Moonpig was founded in 1999, before Lean and Agile approaches had become mainstream in the UK. It was not until about 2013 that Moonpig first began to adopt Agile practices. In this post Amanda Colpoys – a Lean, Agile and Growth Coach, shares her experiences as she set out to introduce business agility at Moonpig.

Agile 40

Agile Lean Engineering 2013 40

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Project Management (#APM). Agile Software Development (#ASD).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Wrike

NOVEMBER 7, 2018

Agile Project Management. Project Management Software & Tools. 19% say Agile techniques. Agile Project Management. 38% of organizations report using agile frequently. [6]. 75% of highly agile organizations met their goals/business intent, 65% finished on time, and 67% finished within budget. Other – 6%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Workzone

AUGUST 4, 2021

This list of alternatives for Asana the project management software will help you identify which project management software you should be using. We’re going to share the top Asana alternative, Workzone, pros and cons of Asana, and 24 other software solutions so you can decide which option is worth researching further.

2021 26

2021 Software Review Technical Review Underperforming Technical Team 26

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

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43