Remove 2013 Remove Software Development Remove Underperforming Technical Team
article thumbnail

Dependency Management – the Good, the Bad, the Ugly

Scrum.org

Does your team struggle to get items to Done? Do they experience a high amount of spill-over into the next cycle because they are waiting on another team or another person? Do items sit in a blocked state and age out while waiting on other teams or people to complete work? Dependencies are an epidemic in software 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. The bad news, it’s hard to master. Scrum is part of agile software development and teams practicing agile.

SCRUM 351
Insiders

Sign Up for our Newsletter

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

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

Top Project Management Conferences of 2020

ProjectManager.com

It’s not a bad practice, but why save it for once a year? A software development conference with workshops on the theme of Our Digital Tomorrow. The conference serves developers, team leads, architects and project managers. For the agile enthusiast, this scrum gathering takes place twice a year since 2013.

2020 289
article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.

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

How Wrike’s Engineers Developed a Unique Quality Control System

Wrike

I joined the team as a QAA engineer in 2010, the first employee in this role. Over the past 12 or so years, we have built a super team of brilliant QAA engineers. The team made a complete audit of everything that could be checked and improved by at least 1%. But he was wrong — Team Sky won in just three. Hello, everyone!