Lean software management case study: Timberline Inc.

This paper is believed to be the first documented account of a full adoption of lean by a software company. Lean techniques were devised by Toyota and other manufacturers over the last 50 years. The techniques are termed lean because they require less resource to produce more product and exceptional quality. Lean ideas have also been successful in service industries and product development. Applying lean to software has been advocated for over 10 years. Timberline, Inc started their lean initiative in Spring 2001 and this paper records their journey, results and lessons learned up to Fall 2003. This case study demonstrates that lean thinking can work successfully for software developers. It also indicates that the extensive lean literature is a valuable source of new ideas for software engineering.

Lean software process

This paper shows how the concepts of lean manufacturing can be successfully applied to software development. The key lean concept is to have a minimum of work in progress, which forces problems into the open. The time is then taken to fix the production system so the errors will not occur again.

Lean principles and techniques for improving the quality and productivity of software development projects: a case study

Software product development is recognised as difficult due to the intangible nature of the product, requirements elicitation, effective progress measurement, and so forth. In this paper, we describe some of the challenges of software product development and how the challenges are being met by lean management principles and techniques. Specifically, we examine lean principles and techniques that were devised by Toyota and other manufacturers over the last 50 years. Applying lean principles to software development projects has been advocated for over ten years and it will be shown that the extensive lean literature is a valuable source of ideas for software development. A case study with a software development organisation, Timberline Inc., will demonstrate that lean principles and techniques can be successfully applied to software product development.

Further assessment of the complement component 2 and factor B region associated with age-related macular degeneration

PURPOSE. Polymorphic variation in genes involved in regulation of the complement system has been implicated as a major cause of genetic risk, in addition to the LOC387715/HTRA1 locus and other environmental influences. Previous studies have identified polymorphisms in the complement component 2 (CC2) and factor B (CFB) genes, as potential functional variants associated with AMD, in particular CFB R32Q and CC2 rs547154, both of which share strong linkage disequilibrium (LD). METHODS. Data derived from the HapMap Project were used to select 18 haplotype-tagging SNPs across the extended CC2/ CFB region for genotyping, to measure the strength of LD in 318 patients with neovascular AMD and 243 age-matched control subjects to identify additional potential functional variants in addition to those originally reported. RESULTS. Strong LD was measured across this region as far as the superkiller viralicidic activity 2-like gene (SKIV2L). Nine SNPs were identified to be significantly associated with the genetic effect observed at this locus. Of these, a nonsynonymous coding variant SKIV2L R151Q (rs438999; OR, 0.48; 95% confidence interval [CI], 0.31- 0.74; P < 0.001), was in strong LD with CFB R32Q, rs641153 (r2 = 0.95) and may exert a functional effect. When assessed within a logistic regression model measuring the effects of genetic variation at the CFH and LOC387715/HTRA1 loci and smoking, the effect remained significant (OR, 0.38; 95% CI, 0.22- 0.65; P < 0.001). Additional variation identified within this region may also confer a weaker but independent effect and implicate additional genes within the pathogenesis of AMD. CONCLUSIONS. Because of the high level of LD within the extended CC2/CFB region, variation within SKIV2L may exert a functional effect in AMD. Copyright © Association for Research in Vision and Ophthalmology.

The component masses of the cataclysmic variable V347 Puppis

We present time-resolved spectroscopy and photometry of the double-lined eclipsing cataclysmic variable V347 Pup ( = LB 1800). There is evidence of irradiation on the inner hemisphere of the secondary star, which we correct for using a model to give a secondary-star radial velocity of K R = 198 +/- 5 km s(-1). The rotational velocity of the secondary star in V347 Pup is found to be v sin i = 131 +/- 5 km s(-1) and the system inclination is i = 84degrees.0 +/- 2degrees.3. From these parameters we obtain masses of M-1 = 0.63 +/- 0.04 M for the white dwarf primary and M-2 = 0.52 +/- 0.06 M for the M0.5V secondary star, giving a mass ratio of q = 0.83 +/- 0.05. On the basis of the component masses, and the spectral type and radius of the secondary star in V347 Pup, we find tentative evidence for an evolved companion. V347 Pup shows many of the characteristics of the SW Sex stars, exhibiting single-peaked emission lines, high-velocity S-wave components and phase-offsets in the radial velocity curve. We find spiral arms in the accretion disc of V347 Pup and measure the disc radius to be close to the maximum allowed in a pressureless disc.

Software project initiation and planning – an empirical study

This study describes a study of 14 software companies, on how they initiate and pre-plan software projects. The aim was to obtain an indication of the range of planning activities carried out. The study, using a convenience sample, was carried out using structured interviews, with questions about early software project planning activities. The study offers evidence that an iterative and incremental development process presents extra difficulties in the case of fixed-contract projects. The authors also found evidence that feasibility studies were common, but generally informal in nature. Documentation of the planning process, especially for project scoping, was variable. For incremental and iterative development projects, an upfront decision on software architecture was shown to be preferred over allowing the architecture to just ‘emerge’. There is also evidence that risk management is recognised but often performed incompletely. Finally appropriate future research arising from the study is described.