Remove 2007 Remove Software Development Remove Software Engineering
article thumbnail

Get To Know Inloox: Martin - Software Engineer and Employee from “Day One”

Inloox

Martin has been working for InLoox since October 2007 and is therefore the oldest employee in our company. Today, he supports our development team as a software architect with his many years of experience. For me, InLoox means continuous development and challenge. Pierre: Software Developer at InLoox.

article thumbnail

Basis of Estimating Software Development

Herding Cats

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

What is IT Service Management?

The IIL Blog

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. Service Integration and Management, aka SIAM, was developed in 2005.

2007 78
article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Software development is (generally speaking) very complex. Why our brain is not built for software engineering. and Vidal, C.

2002 208
article thumbnail

Reading List for the Cone of Uncertainty

Herding Cats

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48
article thumbnail

Assume a Spherical Cow

Leading Agile

The impression was reinforced strongly when I attempted to bridge the divide by participating in the academic tracks of agile and technical conferences in the 2007-2008 time frame. They weren’t professional software developers, and they were pretty new at the whole process of doing research, as well. ” Yeah.