2013 Development Team Review Underperforming Technical Team 
ProjectManager.com
MARCH 4, 2022
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.org
AUGUST 3, 2020
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The IIL Blog
JULY 31, 2024
By Debra Khan Practitioners of content strategy do not have to go it alone when developing a strategy for a content project. 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.
Scrum.org
APRIL 7, 2022
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.
Digite
MAY 15, 2018
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. You should go read it now.
Scrum.org
AUGUST 25, 2022
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.
Scrum.org
MARCH 31, 2020
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.
Expert insights. Personalized for you.
353 
Let's personalize your content