Remove 2010 Remove Examples Remove Software Remove Underperforming Technical Team
article thumbnail

7 Hidden dangers of project management (Or why even well-planned projects sometimes fail)

Rebel’s Guide to PM

Maja Mrsic Here are 3 examples of projects that didn’t go to plan. During a company integration program, customer service levels dropped by 25-50% because the team management focused their efforts on reorganizing and changing employees’ roles and responsibilities, all with “the best of intentions”.

Planning 412
article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

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 332
Insiders

Sign Up for our Newsletter

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

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

How We Made Our Customer The Product Owner

Scrum.org

From 2010–2015 I worked as a Scrum Master for a web agency. We developed software solutions for external clients. When I started with Scrum, I changed my role from Project Manager to Scrum Master, the developers slowly moved from ‘programmers to product developers’, yet the Product Owner role remained challenging to fulfill.

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

The Must-Read Reading List for Project Communication and Collaboration

Rebel’s Guide to PM

. Project teams communicate and collaborate by default, don’t they? That certainly hasn’t been the case for all the teams I have worked on. Don’t assume your project team will know how (or even want to) communicate well and collaborate with each other. This book reminds us that conflict on teams is inevitable.

2013 291
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”.