Remove 2013 Remove 2018 Remove Software Development Remove Underperforming Technical Team
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

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!

Insiders

Sign Up for our Newsletter

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

article thumbnail

43 Learning Resources for New and Experienced Project Managers

LiquidPlanner

Results Without Authority: Controlling a Project When the Team Doesn’t Report to You by Tom Kendrick. Leading a project team that doesn’t report to you is a whole new challenge in itself. Kendrick walks through how to motivate a team to contribute to a project’s success. Cost: Coursera: Agile Development Specialization.

article thumbnail

Risk Management Resources

Herding Cats

Risk Management is essential for development and production programs. This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. 255, April 2010. 920, November 2004. Panaitescu, M.

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

Modeling the Future is the Basis of Project Success

Herding Cats

It's the Planning and Controls processes working together with the Technical Development processes that provide the ability to forecast what should happen in the future if we keep going like we are going now using a Model of the possible future outcomes. 413-426, 2013. 413-426, 2013. This is the desired outcomes model.