Remove 2002 Remove Software Developers Remove Technical Review
article thumbnail

Top 10 Project Management Methodologies – An Overview

ProjectManager.com

We’ll go through some of the most popular project management methodologies, which are applied in many sectors such as software development, R&D and product development. When to Use It: The practice originated in software development and works well in that culture. Top 10 Project Management Methodologies.

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

Software development is (generally speaking) very complex. Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). It is a mental process and a limited mental resource (Ashcraft, 2002). waterfalls) are very likely to fail.

2002 225
Insiders

Sign Up for our Newsletter

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

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 225
article thumbnail

The 23 Best Project Management Books For Upgrading Your Career in 2020

Planio

Swipe to Unlock: The Primer on Technology and Business Strategy. Technical documentation. These books range from technical guides to quick catch-ups on the core principles of project management, from how to gather requirements and plan your timeline to communicating and inspiring your team. Author: Harvard Business Review.

2020 148
article thumbnail

Questioning Agile Dogma

Leading Agile

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? As a result, the organization never benefited from the full potential of the technical staff. Stable Team.

Agile 116
article thumbnail

Introduction to Jira

MPUG

I ventured from a military manufacturing background into the tech industry, initially in a support capacity. Jira’s inception traces back to April 2002, birthed by Atlassian, a company founded by two Australian friends, Mike Cannon-Brooks and Scott Farquhar. Within just three years of its launch, Jira already had 1,000 customers.

article thumbnail

Defensive Programming Grows Up

Leading Agile

Self-organize technical teams on a peer model rather than the Chief Programmer model , to help ensure common understanding and knowledge across the team and to increase the team’s bus number. The level of technical expertise required to use this kind of automation far exceeds that necessary for automating conventional functional checks.