Remove 2011 Remove Software Developers Remove Software Development Remove Underperforming Technical Team
article thumbnail

We are entering the Deployment Phase of the Digital Age

Scrum.org

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. What does that mean for organization structures, team models, and the day-to-day actions of people? . Compare to 2001 there is only one company that is on the list, Microsoft. So what are the implications for how we work?

article thumbnail

Projecting Project Success

MPUG

Although technology and software development tools are essential for most projects, it’s the leadership of a project that makes the difference between a project’s success or failure. Giving employees or teams the right foundational skills is critical to success. These numbers were about the same in 2011.

Insiders

Sign Up for our Newsletter

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

article thumbnail

5 Whys to Explore Scrum with an independent Scrum Caretaker

Gunther Verheyen

Besides having engaged with many teams and organizations I have also created and facilitated many Scrum workshops and classes about various topics for various audiences since then. In 2011 I obtained my license as a Professional Scrum Trainer for Scrum.org from Ken Schwaber (co-creator of Scrum).

SCRUM 80
article thumbnail

A guide to Remote Work in 2020

Binfire

Binfire , after all, has been a remote working environment since we started in 2011. Set working hours when every in your team could be online together. This is easy said than done if your team members are located in multiple time zones. This helps team building and gives the sense to everybody they are working in a team.

2020 78
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. 3, March 2002.

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 366
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.