article thumbnail

Top 10 Project Management Methodologies – An Overview

ProjectManager.com

That’s because what we think of as agile really appeared in 2001 with the publication of the “Manifesto for Agile Software Development,” authored by 17 software developers. The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. Kanban Methodology.

article thumbnail

Remote Work and Scrum

Scrum.org

David Solomon cites the collaborative, innovative, apprenticeship model of Goldman Sachs as not working well in a remote, distributed manner. What is shocking is that this study finds productivity much higher than a 2001 study by Stanfords Nichols Bloom who cited a 13% productivity bump. So is this true?

SCRUM 245
Insiders

Sign Up for our Newsletter

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

article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Each methodology is relevant in its own right, unlocking potential, driving innovation, and ensuring that your projects meet expectations. Feedback Loops – Incorporate regular meetings to review and adapt your workflow based on feedback. Columns might include "Ideation," "Design," "Approval," "Execution," and "Review."

article thumbnail

The Evolution of Project Management

The IIL Blog

When the Department of Defense (DoD) decided to expand the need for more technical projects following World War II, pressure was placed upon the aerospace and defense community to develop expertise in project management. First, the PM was expected to possess a command of technology rather than merely an understanding of technology.

Aerospace 147
article thumbnail

Agile and Scrum: Unravelling the Misconceptions

Scrum.org

Unaware of the true purpose of the Sprint Review and Sprint Retrospective. We'll review some key concepts to help to dispel any confusion. In 2001 the Agile Manifesto for Software Development was introduced to encapsulate a new way of thinking with 4 values and 12 principles on how to deliver software products better.

SCRUM 163
article thumbnail

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

Scrum.org

2001 ) and proactive behavior ( LePine, Erez & Johnson, 2002 ). “So So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. SCRUM and productivity in software projects: a systematic literature review.

Agile 212
article thumbnail

A PM’s Guide to Agile Software Development

Project Bliss

Continuous innovation and improvement are regular practices. It came about during a ski trip in 2001. Continuous attention to technical excellence and good design enhances agility. Today both technology and the marketplace can change quickly. Innovation happens quickly these days, and teams need to be able to adjust.