Epicflow Blog

SEPTEMBER 19, 2022

The second dimension represents the maturity levels based on the Capability Maturity Model developed by the Software Engineering Institute (one of the most popular and widely-accepted models of organizational maturity assessment). Book a call with our expert. . Let’s take a look at these levels. . Level #1: Initial process.

Underperforming Technical Team 52

Underperforming Technical Team Prince2 Risk Management Software Engineering 52

Herding Cats

MAY 8, 2016

Let's put aside for the moment the missing principles of managerial finance, probabilistic decision making, microeconomics of decision making, Real Options, Bayesian decision networks, and other decision making processes used in modern business when spending other people's money. Read the entire book, Learn how to think as an estimator.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

AUGUST 27, 2017

After having worked for outsourcing, consultancy and product companies I believe that creating a place where people really trust each other is easier when software engineers and stakeholders are both part of the same organization. This notion shows that governance is not considered a requirement for the business.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Herding Cats

MAY 10, 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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

FEBRUARY 23, 2016

Software Estimating Taxonomy. How to get a "D" in the Freshman Finance Class. Books for Cost and Schedule Forecasting. How To Estimate Almost Any Software Deliverable in 90 Seconds - here's an example to debunk all those posts that say e can't possibly estimate things we don't knwo the details of. Estimating Accuracy.

Estimate 39

Estimate Risk Management Finance Software Developers 39

Herding Cats

JANUARY 23, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . This is the claim from the book.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37