Remove 2010 Remove 2018 Remove Software Remove Underperforming Technical Team
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.

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. IEEE Transactions on Software Engineering , Vol. 255, April 2010.

Insiders

Sign Up for our Newsletter

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

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. IEEE Transactions on Software Engineering , Vol.

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

On Technical Debt And Code Smells: Surprising insights from scientific studies

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why do software teams?—?despite So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”.

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Product Development (#ProdDev). Agile Software Development (#ASD).

article thumbnail

A Better Microsoft Project: Workload Levelling and Resource-Critical Path

MPUG

If you manage a resource-constrained project, you will often artificially delay activities as to not overwork (or burn out) your team members. Examples are software development, new product development, pharmaceutical clinical studies, telecommunication, research and development, education, and government projects.

2010 52