LiquidPlanner

JANUARY 2, 2018

And yet, we had some significant shifts this year, most notably PMI releasing the sixth edition of “A Guide to the Project Management Body of Knowledge” ( PMBOK® Guide ), alongside the Agile Practice Guide. The much-quoted PMI Talent Gap report states that 15.7 It feels to me like 2017 passed by in a flash. But let’s look forward.

2018 106

2018 Certification 2011 Prince2 106

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. requires making estimates) ? De Meyer, C. 24, 2010. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Epicflow Blog

MAY 14, 2019

Looking ahead while planning the project can help you develop a viable risk management strategy and eliminate constraints. Here are the top books recommended by our survey participants: Industrial Megaprojects: Concepts, Strategies, and Practices for Success by Edward W. Facts and Fallacies of Software Engineering by Robert L.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75