An ideal case. (part 1 in the series including 1, 2, 3, 4) Let’s imagine an ideal scenario for software development. In this scenario, there are some users who have real needs that you can identify. Further, some of these users are paying customers who will gladly give you money if you can deliver value to them. You can express their needs as a set of criteria to be satisfied, and these criteria can be measured. Your customers bring you their business because: not only do you promise to identify what they want and build them a solution, you also promise to deliver a solution quickly. The flow of information is something like: latent demand -> characterized demand -> value-adding design -> production -> deployed solution …and your goal is to have smooth and continuous flow through this process, gently accelerating for all eternity.
That is only a very high level description. As information flows through the system, we must have some representation of it: …or… what does the user want? What is Lean - Principles. Lean forklaret for sjuskehoveder - Kommunikationsforum. Lean er et begreb du lige så godt kan forholde dig til. For det komme rogså til dig på et tidspunkt. Her er en stribe artikler og links om lean (klik på fx artikler i feltet for at få listen): Lean på kforum.dk & her er en tidligere artikel, der giver dig overblik over emnet på 10 minutter: Begrebet lean er opfundet af forskerne Jim Womack og Daniel Jones.
De havde registreret, hvordan Toyotas produktion af biler foregik langt billigere end hos alle konkurrenterne. De satte sig derfor for at undersøge fænomenet. De fandt ud af, at Toyota brugte et bestemt system, hvor fokus i alle sammenhænge var på at minimere spild. Forbedringer på 50 % Det er 40 år siden, Toyota begyndte at arbejde med at trimme virksomheden. De fem principper i lean Lean blev i første omgang udviklet i Toyotas industriproduktion som fem grundlæggende principper. Forstå, hvad der skaber værdi for kunderne og se den værdikæde, hvormed råvaren tilføres værdi frem til, at kunden får dækket sit behov.
Husmetaforen 7. 8. Lean software development. Lean software development (LSD) is a translation of lean manufacturing and lean IT principles and practices to the software development domain. Adapted from the Toyota Production System,[1] a pro-lean subculture is emerging from within the Agile community. Origin[edit] The term lean software development originated in a book by the same name, written by Mary Poppendieck and Tom Poppendieck.[2] The book presents the traditional lean principles in a modified form, as well as a set of 22 tools and compares the tools to agile practices. The Poppendiecks' involvement in the Agile software development community, including talks at several Agile conferences [3] has resulted in such concepts being more widely accepted within the Agile community. Lean principles[edit] Lean development can be summarized by seven principles, very close in concept to lean manufacturing principles: Eliminate waste[edit] In order to eliminate waste, one should be able to recognize it.
Amplify learning[edit] See also[edit]