Scrum.org

AUGUST 13, 2019

The first part contains my personal journey in becoming a Scrum Master, the second part includes recommendations for new Scrum Masters. Part 1 — Becoming a Scrum Master. Nine years ago I changed my title from Project Manager into Scrum Master. Do you have any recommendations for my Scrum Master journey?”.

SCRUM 118

SCRUM Certification Telecoms Agile 118

International Institute for Learning

APRIL 19, 2023

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. They offer practitioners tools to extend and mature their agility beyond the team to programs and the broader enterprise. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM.

Agile 59

Agile Cadence Certification Lean 59

EasyProjects

SEPTEMBER 24, 2019

If you follow the instructions to a tee, it’s going to taste fantastic – just like the reviews say. There are three main agile methodologies to consider: Scrum, Kanban or Extreme Programming. Scrum is used by software development teams. In Review ? Sprint Review. Disgusting. Salesforce .

Agile 41

Agile Technical Review Software Review Underperforming Technical Team 41

Scrum.org

APRIL 7, 2022

Considering just how popular the notion of fluid teams has become, I think it is important to weigh the evidence that supports it or contradicts it. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. The need for fluid teams. It takes time to develop teams.

Underperforming Technical Team 167

Underperforming Technical Team 2007 2006 2009 167

Agilemania

NOVEMBER 30, 2021

It was, for this reason, Dean Leffingwell decided to conceptualize SAFe® in 2011. Planning and Execution of Program Increment: A SAFe Agilist has envisioned a roadmap for the success of the Agile Development and successful SAFe implementation process. Improves product development flow. Creation of innovative solutions.

Cadence 98

Cadence Lean 2011 Construction 98

International Institute for Learning

SEPTEMBER 20, 2022

Regarding the right size of a team, it has been experienced that a good number is around 10. For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52