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 2004 2002 141

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Don't hear one?

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

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. 920, November 2004. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

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

The IIL Blog

APRIL 27, 2018

Online gaming collaboration can be traced back to the introduction of the personal computer and software developers and came to life in the early 1990s when the Internet was introduced. Resources: Number of participants, software, and systems required, facilities, etc. agile retrospectives).

Software Review 121

Software Review 2004 2012 PMI 121

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. An Introduction to IMP/IMS , 17 Oct 2004. Agile Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. So much that it is being used for other projects besides software development. To become agile, it is important to implement the feedback loops. However, after 1940 David J.

Software Review 81

Software Review Technical Review 2004 SCRUM 81

EasyProjects

SEPTEMBER 19, 2018

My team and I were running a software development company back in 2004 when we realized that our projects needed to be managed in a better way. Once we started using Easy Projects to manage our software development projects, our clients started requesting access to use it for their own work.

Artificial Inteligence 40

Artificial Inteligence 2004 2015 Infrastructure 40

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

Leading Agile

MARCH 11, 2020

Agile Unplugged is your chance to explore LeadingAgile’s freshest ideas, mental models, frameworks, and solutions with the people that are actually doing the work of leading large-scale Agile Transformation, out in the field. What was that, probably 2004, or ’05 or something in that kind of range, I think?

Agile 103

Agile Fractional CTO CTO Hire Influencer 103

Gunther Verheyen

FEBRUARY 27, 2024

As the earlier excerpt shows, it was this book that introduced the idea of applying the practices described by Takeuchi and Nonaka to software development. The authors explain why the waterfall model doesn’t work for software development, and they offer possible alternatives, among them (what they call) Scrum. 20, 2004: pp.

SCRUM 71

SCRUM 2004 Software Review 2019 71

MPUG

DECEMBER 3, 2021

He joined Edwards in 2004 as a project coordinator and scheduler and provided project planning and scheduling support to variety of commercial and federal government clients. If you are using agile, you’re not going to necessarily have a lot of requirements at once. Walter’s certifications include the PMP and MCTS.

Software Review 52

Software Review Technical Review Underperforming Technical Team Risk Management 52

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development,” Pongtip Aroonvatanaporn,” Ph.D.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Scrum.org

AUGUST 17, 2020

It happens, for example, when we don’t trust a certain person or group of people, and then only see behavior that fits with our belief (or even interpret it as such) without considering observations where they don’t (Oswald & Grosjean, 2004). 2004), “Confirmation Bias” , in Pohl, Rüdiger F. (ed.), 79 (386): 259–267. Nisbett, R.

2015 217

2015 2014 2004 Influencer 217

Scrum.org

JANUARY 27, 2021

As the world became more complicated, we created automation using machinery with software to control it. In the complex world of Sales, Marketing, and Software Development, we also needed new ways of thinking that would power the same ideas from Toyota and Lean into the high variance world of complex cognitive work. Ralph Stacy Model.

2001 211

2001 Software Review Technical Review Underperforming Technical Team 211

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. Why our brain is not built for software engineering. Cognitive paradigms, applied to Scrum / Agile. 2004) _How can we think the complex?Retrieved

2002 197

2002 SCRUM 2007 2003 197

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

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." Macroeconomics is not. .

Software Developers 34

Software Developers Software Development Risk Management Risk 34

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. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 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

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Paymo App

SEPTEMBER 8, 2017

Launched in 2004, it’s aimed at giving you a better handle on your business and the work your teams are doing. There are no options for Kanban boards either, so teams used to Agile approaches could struggle. Cloud-based collaboration and project management software that scales across teams in any business. Pricing and Plans.

Software Review 104

Software Review Technical Review 2017 2016 104

Wrike

DECEMBER 7, 2009

Demos, a British think tank, described this in a 2004 report as a key moment in the arrival of a “Pro-Am” era, a time when professionals and amateurs work side by side: “Astronomy used to be done in ‘big science’ research institutes. When people ask me about the primary area of Project Management 2.0

Retail 28

Retail 2004 Construction Risk Management 28