Remove 2014 Remove 2020 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

The 23 Best Project Management Books For Upgrading Your Career in 2020

Planio

We combed through best-seller lists, spoke with veteran PMs, and read a ton to put together this list of the best project management books for upgrading your career in 2020. The Five Dysfunctions of a Team: A Leadership Fable. The best books for building better habits (for yourself and your team). Gantt Chart. Scope of Work.

2020 148
Insiders

Sign Up for our Newsletter

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

article thumbnail

Complete Collection of Project Management Statistics 2015

Wrike

Keys to Project Success: 48% say the team’s technical skills. 26% say effective team communication. Lean & Test Driven Development (TDD) – 11%. Feature Development Driven – 9%. Dynamic Systems Development Method – 3%. Poor visibility & resource management : 31%. Poor purchasing processes: 23%.

2015 60
article thumbnail

Vendor Showcase Recap: Making Light Work of Schedule Risk Analysis – By Barbecana

MPUG

Kyle: John joined Barbecana as CLO in 2014, and assumed the role of President, and CEO in 2019. He has extensive experience of both project management, and software development. It’s got nothing to do with poor estimates, poor execution, and so on. So this is a poor technique, you shouldn’t do it.

Risk 52
article thumbnail

Vendor Showcase Recap: Making Light Work of Schedule Risk Analysis – By Barbecana

MPUG

Kyle: John joined Barbecana as CLO in 2014, and assumed the role of President, and CEO in 2019. He has extensive experience of both project management, and software development. It’s got nothing to do with poor estimates, poor execution, and so on. So this is a poor technique, you shouldn’t do it.

Risk 52