Lean Software Development--Building and Shipping Two Versions.

The article presents a model of lean software development which focuses on differentiating the methods of designing the prototype and second version of a given project. The author highlights how prototypes and subsequent versions are fundamentally approached differently, how different computer progr...

Full description

Bibliographic Details
Published in:Communications of the ACM Vol. 58; no. 12; pp. 56 - 59
Main Author: MATSUDAIRA, KATE
Format: Article
Published: Association for Computing Machinery Dec2015
Subjects:
Online Access:View this record in EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=111183907&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 111183907
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Dec2015
      vid: 58
      iid: 12
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        111183907
        10.1145/2814346
      ppf: 56
      ppct: 3
      formats:
      tig:
        atl: Lean Software Development--Building and Shipping Two Versions.
      aug:
        au: MATSUDAIRA, KATE
        affil: Founder, Popforms.
      su:
        Lean management
        Computer software development
        Computer software developers
        Prototypes
        Software versioning
        Overproduction
        Prevention
        Attitude (Psychology)
      sug:
        subj:
          Lean management
          Computer software development
          Computer software developers
          Prototypes
          Software versioning
          Overproduction
          Prevention
          Attitude (Psychology)
      ab: The article presents a model of lean software development which focuses on differentiating the methods of designing the prototype and second version of a given project. The author highlights how prototypes and subsequent versions are fundamentally approached differently, how different computer programmers are more aligned to either one of the design phases, and how this v1/v2 process minimizes over-engineering.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2015
    holdings:
      @attributes:
        islocal: N