Remove Governance Remove Logistics Remove Project Life Cycle Remove Software Development
article thumbnail

Kanban vs. Scrum: What’s the Difference?

ProjectManager.com

The scrum methodology has been around since the mid-1980s and has been a core sub-methodology of agile since 2001 when Ken Schwaber and Mike Beedle wrote the book on it: Agile Software Development with Scrum. That hasn’t stopped practitioners from using scrum in varying industries, from retail logistics to event planning.

SCRUM 411
article thumbnail

Top 10 Project Management Methodologies – An Overview

ProjectManager.com

Some of them work better on particular industries or projects, so you’ll need to learn about project management methodologies to decide which one works best for you. Top 10 Project Management Methodologies. If you manage projects, you need to learn about project management methodologies. Kanban Methodology.

Insiders

Sign Up for our Newsletter

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

article thumbnail

What is Project Management

MPUG

The PMI also notes that a project is typically different from ongoing operations or business as usual and that it requires the coordination of various resources and activities in order to achieve its objectives. From start to finish, a project usually goes through 5 phases, called the Project Life Cycle.

article thumbnail

Risk Management Resources

Herding Cats

“Deliberate Ignorance in Project Risk Management,” Elmar Kutsch and Mark Hall, International Journal of Project Management , Volume 28, Issue 3, pp. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 255, April 2010.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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. 255, April 2010. 920, November 2004. Kwak and J.