Remove 2011 Remove Agile Remove Development Team Review Remove Process
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. Scrum is part of agile software development and teams practicing agile. Scrum Values.

SCRUM 335
article thumbnail

A Beginner’s Guide to Scrum Ceremonies

ProjectManager.com

Scrum ceremonies are meetings that are unique to scrum teams. Scrum ceremonies ensure that everyone (the scrum master, product owner and development team) is in-sync. A sprint employs four different scrum ceremonies to ensure proper execution: sprint planning, daily scrum, sprint review and sprint retrospective.

SCRUM 203
Insiders

Sign Up for our Newsletter

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

article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

By Alan Zucker Disciplined Agile® (DA) and the Scaled Agile Framework (SAFe®) are two popular, second-generation agile methodologies. They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. They emerged about a decade after the Agile Manifesto.

Agile 59
article thumbnail

Benefits of Scaled Agile Framework ( SAFe®) – Agilemania

Agilemania

The year was 2011 and there was a pressing need for a scaling framework that could help large organizations design efficient systems to build enterprise level products/solutions to cater to customer’s rapidly changing needs. He introduced the Scaled Agile Framework (SAFe). SAFe is based on following 10 Lean-Agile principles-.

article thumbnail

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

Scrum.org

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime. The need for fluid teams.

article thumbnail

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

Scrum.org

Work agreements are basically team-agreed expectations on how you will behave, interact and deal with certain scenarios. Some find the process of creating them “childish” or “a waste of time”. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. And there is some truth to that.

2004 225
article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

Also, we have quite diverse roles in the team (i.e., In the usual Scrum process, the P.O. Starting in 2007 when we moved from being a waterfall shop to 2011 when we adopted Kanban, we have ourselves mastered a number of challenges that the question above presents. Dev Lane for the main dev activity.