Epicflow Blog

MAY 14, 2019

Actually caring about the needs of your sponsor,” says Alberto Pérez Veiga , an IT Engineer at NATO Communications and Information Agency. I saw many lists of thousands of improperly documented LL which are not manageable and thus not useful because of the quality and level of details of the information provided.”.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

MARCH 11, 2017

Our perception of this world - the data and information we receive about these behaviors. Information about key project cost, performance, and schedule attributes is often uncertain or unknown until late in the program. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C. Dorofee, et.

Risk Management 35

Risk Management Risk Technical Review 2002 35