Remove Development Team Review Remove Groups Remove Process
article thumbnail

The 12 Agile Principles: Definitions & How to Use Them

ProjectManager.com

Agile is a project management methodology that allows development teams to set up a dynamic work management framework. Our kanban boards are great for agile teams. Managers get visibility into their process so they can reallocate resources as needed to avoid bottlenecks. Agile Processes Promote Sustainable Development.

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. For this purpose it defines three roles, a scrum master, a product owner and a development team, made up of several team members.

SCRUM 353
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Project Prioritization for PPM (Matrix Included)

ProjectManager.com

Thankfully, there’s project prioritization to help guide your decision-making process. Let’s take a look at the process for project prioritization and the various models you can use to judge the viability of potential projects. The same process can be applied to tasks in a single project. Project Prioritization Process.

article thumbnail

Phase-Gate Process in Project Management: A Quick Guide

ProjectManager.com

When you have a long-term project that needs to be evaluated regularly, and you’re dealing with numerous stakeholders, the phase-gate process could be an ideal fit for your organization. What is the Phase-Gate Process? It is typically used for new product developments, software/app/website launches and business-wide changes.

article thumbnail

15 Sprint Review Anti-Patterns

Scrum.org

TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?

article thumbnail

Sprint Planning 101: How to Plan Great Sprints

ProjectManager.com

A sprint is an iteration in the development cycle of a project. The sprint is defined by a small amount of planned work that the team has to complete and ready for review. Teams work collaboratively to complete the sprint and have it ready for review. Once the sprint is finished, there’s a sprint review meeting.

Planning 251
article thumbnail

Where to measure throughput in the sprint backlog

Scrum.org

According to the Scrum Guide, the Definition of ‘Done’ “is used to assess when work is complete on the product Increment.”. Or should it be measured when the development hands off the PBI to another team/group? In my first scenario, we have a Scrum team that ships almost daily done PBIs into a production environment.