Herding Cats

MAY 10, 2019

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. 5, September/October 2011. (Making these decisions in the presence Uncertainty ?

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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.

Risk Management 35

Risk Management Risk Technical Review 2002 35

LiquidPlanner

JANUARY 2, 2018

million new project management roles will be created between 2011 and 2020, so we’re still expecting to see growth in the next couple of years. Industries like construction, software engineering, and consultancy probably see this as less of an issue. The much-quoted PMI Talent Gap report states that 15.7

2018 106

2018 Certification 2011 Prince2 106

Wrike

SEPTEMBER 29, 2022

The software makes it easy to customize your workspace to reflect your branding and tackle your needs. Rather than changing your processes to fit the software, you customize Wrike to fit your business. . Asana was launched in 2011 by co-founders Dustin Moskovitz and Justin Rosenstein. What is Asana?

2006 36

2006 2011 Software Budget 36

Epicflow Blog

MAY 14, 2019

Merrow (Wiley, 2011), recommended by Giorgio Locatelli , an Associate Professor of Infrastructure Procurement and Management at the University of Leeds. Facts and Fallacies of Software Engineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Scrum.org

FEBRUARY 4, 2022

Perhaps you’ve read many blog posts about how horrible SAFe is, or how useless estimation is, or what the optimal size of a team is. Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011).

Agile 189

Agile Software Review Underperforming Technical Team Technical Review 189

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. Patnail, International Journal of Software Engineering, IJSE, 8.1,

Estimate 40

Estimate Software Review Software 2012 40