article thumbnail

Why Agile Engineering Practices in Software Development Are Essential to Achieve Agility

Scrum.org

Either way, it is questionable that an agile process without underlying agile practices applied can be agile at all. For sustainability, robustness, quality, customer service, fitness for purpose and true agility in software development teams, it is important for there to be continuous investment in agile engineering practices. [1]

article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

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 335
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Basis of Estimating Software Development

Herding Cats

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.

article thumbnail

Practical Fibonacci: A Beginner's Guide to Relative Sizing

Scrum.org

A traditional or Waterfall software development lifecycle includes a long and detailed planning period to define requirements before beginning development. It’s a different approach than a traditional software lifecycle, but it is necessary. 2006, Jørgensen and Grimstad). Trust the Team and the Process.

article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

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.

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

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.

article thumbnail

Systems Thinking in Organizational Coaching

Scrum.org

A software development effort is always a system! Small changes can produce big results—but the areas of highest leverage are often the least obvious (Peter Senge, The Fifth Discipline, 2006). Patterns are often the result of the organizational structure, processes and policies the people work in.

2006 215