Digite

JANUARY 7, 2018

hours, Published 2014 by Blue Hole Press). This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. Principle of Product Development Flow. 290 pages, Published 8 May 2014 by Celeritas Publishing). Kanban from the Inside.

Lean 79

Lean Software Review 2010 2014 79

Herding Cats

MAY 10, 2019

“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. 1, March 2014. 5, September/October 2011. 255, April 2010.

Risk Management 38

Risk Management Risk Technical Review 2004 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 2004 35

Herding Cats

MARCH 11, 2017

Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46

2003 2014 2011 2015 46

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. And money in the bank is what software development is about. Traditional software development processes are like watchmaking. 6, No 5, October 2014. [3]

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64