Remove Books Remove Development Team Review Remove Software Development Remove Underperforming Technical Team
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. The bad news, it’s hard to master. Scrum is part of agile software development and teams practicing agile.

SCRUM 338
article thumbnail

My Experience With Growing A Developer Culture

Scrum.org

For years, I’ve fulfilled the role of Scrum Master for many different organizations and Scrum Teams. These teams were mostly focused on software development. These organizations were able to attract the smartest developers and create products customers loved. Examples of a Developer Culture.

Insiders

Sign Up for our Newsletter

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

article thumbnail

A Review Of Scrum For Kanban Teams

Digite

In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. Disclaimer.

article thumbnail

6 Steps for a Solid Code Review Process

Wrike

Imagine you’re writing a book and you’ve just finished your first draft. The code review process is like the editing phase in writing a book. The code review process is like the editing phase in writing a book. You give it to someone else to read — this person is like the code reviewer.

article thumbnail

What is Agile Project Management?

The IIL Blog

The History of Agile Project Management Agile project management emerged in the software development industry in the late 1990s and early 2000s. In 1991 the book Rapid Application Development was published and an approach of the same name, RAD, was born. Agile projects are iterative and have regular feedback loops.

Agile 88
article thumbnail

70 Scrum Master Theses

Scrum.org

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. As somebody hiring for a Scrum Team, you need to determine for yourself what works for your organization — which is a process, not a destination. Generally, insisting that the team achieve specific KPI, e.

SCRUM 222
article thumbnail

Scrum’s Nature: It Is a Tool; It Is Not About Love or Hate

Scrum.org

Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain. These rigid methodologies inevitably turn developers into mindless cogs in a corporate machinery—churning out more and more code—while ignoring the true potential of these knowledge workers.