Remove 2012 Remove 2017 Remove Software Developers 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 a growth mindset has helped in my journey to become a PST

Scrum.org

In summary, the person with a growth mindset believe that new abilities can be developed through practice. . In 2017, I decided to raise the bar and embrace the biggest challenge in my career so far. In 2017 my English was an intermediate level. . Embrace challenges. . You love this!”. Step one - The interview. .

2017 175
Insiders

Sign Up for our Newsletter

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

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!

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. 1, March 2014.

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. This is the desired outcomes model. So the open question is. Which comes first?

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. But each method needs to be based on 5 Immutable principles to be successful, no matter the domain or context, PMI Spring Seminar , 2012, Austin TX.