Herding Cats

MAY 10, 2019

México, 1 al 3 de Febrero de 2006. 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. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. De Meyer, C. Loch, and M.

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. México, 1 al 3 de Febrero de 2006. De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Planio

JULY 22, 2020

Influence: The Psychology of Persuasion. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Influence: The Psychology of Persuasion. Published date: 2006 (Revised edition).

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42