Remove 2013 Remove Agile Remove Development Team Review
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 353
article thumbnail

Dependency Management – the Good, the Bad, the Ugly

Scrum.org

There could be many reasons why - perhaps your organization has adopted an Agile framework, but you're not yet structured to support sustainable teams. You may have a strong reliance on vendors or specialists when you start your Agile journey. As you scale your Agile efforts, the dependencies scale as well.

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

We are Not Alone: The Intersection of Project Management and Content Strategy

The IIL Blog

While our tools and techniques might have evolved since 2013, content strategists can find value in looking closely at the basic principles of project management. Based on the needs analysis, project leadership typically develops a business case and charters a project. With the latter, the charter might evolve over time.

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. It takes time to develop teams.

article thumbnail

What Makes A Good Product Owner?

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. How much time should they spend with their team or with stakeholders? Which activities can be fulfilled by others in the team, and what is needed for that? Data from our Scrum Team Survey may shed a light on this.

2014 233
article thumbnail

Working Remotely? This Will Hit You Next!

Scrum.org

Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.

article thumbnail

A Review Of Scrum For Kanban Teams

Digite

In case you haven’t read Yuval’s post, basically, it presents a map of values and practices in Scrum to Kanban language, and encourages Kanban teams to approach Scrum from a practices point of view. As I wrote in 2013, Scrum and Kanban both share a use of values to encourage users of the methods to behave a certain way.