Gunther Verheyen

DECEMBER 17, 2020

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141

2010 SCRUM 2002 2004 141

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). July 2013). ” Software Development 9(8): 28-32. By Luigi Morsa.

Innovation 59

Innovation Agile 2002 2001 59

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days. “The

Estimate 64

Estimate 2006 2005 2013 64

Scrum.org

AUGUST 3, 2020

Dependencies are an epidemic in software development. Sutherland, Scrum Guide, 2013. Do they experience a high amount of spill-over into the next cycle because they are waiting on another team or another person? Do items sit in a blocked state and age out while waiting on other teams or people to complete work? Schwaber and J.

Underperforming Technical Team 245

Underperforming Technical Team Technical Review Software Review Development Team Review 245

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

Productivity Land

FEBRUARY 26, 2024

And despite all remote work challenges , software developers have much to offer. This popular collaboration software offers multiple features and free and paid plans. Taken from: [link] What Is Slack Software? Slack is a messaging program for bringing work communication into one place, launched in 2013.

Software Review 75

Software Review 2013 2024 Controlling 75

Gunther Verheyen

SEPTEMBER 16, 2022

Regardless whether free-floating opportunists like it or not, there is no denying that the source and roots of all things ‘Agile’ is the “ Manifesto for Agile Software Development ”, or the “ Agile Manifesto ” in short. 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

Scrum was instrumental in embracing software development as a form of new product development, and thus as complex work. Software and (new) product development are a subset of complex challenges, but the use of Scrum is not limited to it. The rules of the game are well documented.

SCRUM 110

SCRUM 2003 2010 2013 110

MPUG

MAY 10, 2022

Scrum was originally used in software development projects. Organizations may also choose to adopt various methodologies to begin managing in an Agile way. For example, Scrum is a methodology which emphasizes delivery in short increments and frequent meetings.

Agile 59

Agile 2019 2013 Software Review 59

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Recent trends of Risk Management in Software Development: An Analysis,” Raghavi Bhujang and V.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Scrum.org

APRIL 7, 2022

However, several studies show that cohesion positively impacts performance only in later stages of team development (e.g. This corresponds with research on autonomous teams, as well as principles of Agile software development. 40 years of storming: a historical review of Tuckman’s model of small group development.

Underperforming Technical Team 176

Underperforming Technical Team 2007 2006 2009 176

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 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. 920, November 2004. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. 12, 2008. “A

2003 46

2003 2014 2015 2011 46

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.

Prince2 81

Prince2 SCRUM 2001 Agile 81

Teamweek

JUNE 17, 2020

” LinkedIn founder Reid Hoffman talked about his agile, project-based hiring approach in a 2013 Harvard Business Review article , explaining that he hires employees on a four-year “tour of duty,” with a check in after two years. The terminology is borrowed from software developers.

Technical Review 90

Technical Review 2013 Consulting Innovation 90

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

MARCH 17, 2019

Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015. Integrating Agile with EVM , EVM World, 2013.

2003 54

2003 2011 2008 Performance Measurement 54

Scrum.org

AUGUST 17, 2020

All drivers consider their own driving skills above average (Roy & Liersch, 2013). The Dunning-Kruger effect manifests when people without any experience with software development make strong claims about how easy a particular change should be. Many forms of micro-management are examples of this effect as well. Liersch, M.

2015 225

2015 2014 2004 Influencer 225

Gunther Verheyen

FEBRUARY 26, 2024

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. In 2011 I obtained my license as a Professional Scrum Trainer for Scrum.org from Ken Schwaber (co-creator of Scrum).

SCRUM 74

SCRUM Certification 2016 2011 74

Wrike

NOVEMBER 7, 2018

The number of firms with a PPM process in place grew from 64% in 2003 to 71% in 2013. [13]. Why a Majority of Business and IT Teams Anticipate Their Software Development Projects Will Fail. ESI International: Annual Salary Survey 2013. ESI International: Talent Drain Fact Sheet 2013. Healthcare – 76%. March, 2014.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

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

Herding Cats

SEPTEMBER 25, 2018

2] Modified from Gilberto Montibeller, "7 Sins of assessing performance of Strategies," Jyväskylä International Summer School, 2013, Modelling Strategic Decisions, contained in "Value-Focused Thinking as a Problem Structuring Methods," MarkusHartikainen, Postdoctoral Researcher, University of Jyväskylä. [3] Keeney and Robin S.

2009 34

2009 Artificial Inteligence 2013 2005 34

Paymo App

SEPTEMBER 25, 2017

Year of foundation: 2013. Kunder started out in 2013 as a three person Software as a Service (SaaS) company with one idea: to provide companies with feedback tools for their clients. The tipping point was when Banco de Chile, one of Chile’s largest banks, contacted them to develop a small solution. Employees: 50.

Estimate 0

Estimate 2013 2014 2017 0

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. Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development," Pongtip Aroonvatanaporn," Ph.D. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

International Institute for Learning

SEPTEMBER 20, 2022

Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002. Rich Karlgaard, “Team Management: Think Small and Agile”, forbes.com, Nov 13, 2013. Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. Schwaber, K. Hackman, J. The design of work teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

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

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.

Agile 110

Agile Technical Review Cadence Software Review 110

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

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.

2014 38

2014 2013 2012 Engineering 38

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

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. . And from his project's data that may well be true.

2007 42

2007 2012 2006 2008 42

MPUG

JUNE 20, 2022

Examples are software development, new product development, pharmaceutical clinical studies, telecommunication, research and development, education, and government projects. I repeated this request in later editions under the same title, and again in my new textbooks Forecast Scheduling 2010, 2013, and 2018.

2010 52

2010 Aerospace Underperforming Technical Team Governance 52

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

APRIL 4, 2019

Lechler, Ting Gao, and Barbara Edington, Project Management Institute, 2013. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996. Risk Management in Software Development Projects , John McManus, Routledge, 2003. The Silver Lining of Project Uncertainties, Thomas G.

Risk Management 43

Risk Management Risk 2003 2011 43

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

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