Remove 2011 Remove Analysis Remove Process Remove Software Development
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 206
article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

Some find the process of creating them “childish” or “a waste of time”. Note that we’re using functional job titles here for clarity; not all companies use them, and the Scrum Guide only talks about “developers”. You can fast-track this process with good work agreements. In Achieving Quality in Software (pp. Kearney, E.,

2004 230
Insiders

Sign Up for our Newsletter

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

article thumbnail

Without a Root Cause Analysis, No Corrective or Preventive Action is Credible - Part 1

Herding Cats

This first post is a follow-on from the posts Root Cause of Project Failure , Root Cause Analysis , Discovering the Root Cause - The 5 Whys , T urning Editorials into Root Cause Analysis , Observation Issues and Root Cause Analysis , Without a Root Cause Analysis, No Suggested Fix Can Be Effective. References .

2014 45
article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Economics is a social science concerned chiefly with description and analysis of the production, distribution, and consumption of goods and services. Making changes late in the development cycle has significant impacts on the verification and validation of the system no matter the software development method. .

article thumbnail

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

Scrum.org

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner. The need for fluid teams.

article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011.

2003 54
article thumbnail

The Roles and Responsibilities of a SAFe Agilist You Never Knew

Agilemania

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. A SAFe Agilist applies Lean, Agile, and the Product Development flow principles to improve productivity, employee satisfaction, time to market, and quality. Kanban is a preferred framework for implementing Agile and DevOps software development.

Lean 98