Lean Software Development
Posted on May 30, 2006 Comments (2)
We have posted on the topic of Lean Software Development previously:
David Carlton has an interesting post on this topic: lean software development.
Software development can be extremely complicated and can benefit greatly from making problems visible – jidoka. Inventory is not the key to hiding problems in software development. It might be in the “production of software” but so much software is “produced” and distributed over the internet without producing inventory etc. that the production step is not the main source of problems and longer (in the past boxed software had the same inventory problems other industries experience today). Yet all of us using software have many experiences with the problems users have with software (often on a daily basis). Lean thinking has a great deal to offer for those involved in software development.
By the way, if you are interested in lean application development and are looking for a job in the Washington DC area see, job announcement for a programmer (dead link removed), and maybe we can work together – John Hunter.
Related:
- Management Science for Software Engineering
- Innovation in Software Development Process
- Management Training Program (Fogcreek Software)
Categories: Lean thinking, Management, Management Articles, Software Development
2 Responses to “Lean Software Development”
Leave a Reply
RSS Feed
March 18th, 2010 @ 7:19 am
“a Lexus contains 14 million lines of code, comparable to banking and airplane software systems. Ishi-san concluded that “Therefore Toyota needs to become an IT company…”
January 27th, 2011 @ 10:29 am
[...] Agile software development has teams estimate the effort to deliver requests from the product owner. The estimates are done in points (in order to abstract away from hours – as estimates have plenty of variation in how long they will really take). Then the teams capacity (velocity) is determined based on looking at how many points they complete in a “sprint” (a set length, often 2 weeks). Then the product owner can prioritize all of the requests with an understanding of how much effort each is estimated to take and the historical capacity of the development team. [...]