MARC details
| 000 -LEADER |
|---|
| fixed length control field |
06818cam a2200409 i 4500 |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20221109183143.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
100902s2010 njua b 001 0 eng d |
| 010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
|---|
| LC control number |
2009035319 |
| 011 ## - LINKING LIBRARY OF CONGRESS CONTROL NUMBER [OBSOLETE] |
|---|
| Local cataloguing issues note |
BIB MATCHES WORLDCAT |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
0321620704 |
| Qualifying information |
pbk. (alk. paper) |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9780321620705 |
| Qualifying information |
pbk. (alk. paper) |
| 035 ## - SYSTEM CONTROL NUMBER |
|---|
| System control number |
(OCoLC)406138672 |
| 040 ## - CATALOGING SOURCE |
|---|
| Original cataloging agency |
DLC |
| Language of cataloging |
eng |
| Description conventions |
rda |
| Transcribing agency |
DLC |
| Modifying agency |
YDX |
| -- |
CDX |
| -- |
ATU |
| 050 00 - LIBRARY OF CONGRESS CALL NUMBER |
|---|
| Classification number |
HD30.213 |
| Item number |
.P65 2010 |
| 082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
658.4038011 |
| Edition number |
22 |
| 100 1# - MAIN ENTRY--PERSONAL NAME |
|---|
| Personal name |
Poppendieck, Mary |
| Fuller form of name |
(Mary B.) |
| Relator term |
author. |
| 9 (RLIN) |
506065 |
| 245 10 - TITLE STATEMENT |
|---|
| Title |
Leading lean software development : |
| Remainder of title |
results are not the point / |
| Statement of responsibility, etc. |
Mary and Tom Poppendieck. |
| 264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE |
|---|
| Place of production, publication, distribution, manufacture |
Upper Saddle River, N.J. : |
| Name of producer, publisher, distributor, manufacturer |
Addison-Wesley, |
| Date of production, publication, distribution, manufacture, or copyright notice |
[2010] |
| 264 #4 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE |
|---|
| Date of production, publication, distribution, manufacture, or copyright notice |
©2010 |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
xxii, 278 pages : |
| Other physical details |
illustrations ; |
| Dimensions |
24 cm. |
| 336 ## - CONTENT TYPE |
|---|
| Content type term |
text |
| Content type code |
txt |
| Source |
rdacontent |
| 337 ## - MEDIA TYPE |
|---|
| Media type term |
unmediated |
| Media type code |
n |
| Source |
rdamedia |
| 338 ## - CARRIER TYPE |
|---|
| Carrier type term |
volume |
| Carrier type code |
nc |
| Source |
rdacarrier |
| 490 1# - SERIES STATEMENT |
|---|
| Series statement |
Addison-Wesley signature series. |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc. note |
Includes bibliographical references (pages 247-255) and index. |
| 505 00 - FORMATTED CONTENTS NOTE |
|---|
| Title |
Systems Thinking -- |
| -- |
A Different Way to Run an Airline -- |
| -- |
Customer Focus -- |
| -- |
Who Are Your Customers? -- |
| -- |
Customers Who Pay for the System -- |
| -- |
Customers Who Use the System -- |
| -- |
Customers Who Support the System -- |
| -- |
Customers Who Derive Value from the System -- |
| -- |
What Is Your Purpose? -- |
| -- |
What Is the Nature of Customer Demand? -- |
| -- |
Failure Demand -- |
| -- |
Value Demand -- |
| -- |
System Capability -- |
| -- |
What Is Your System Predictably Achieving? -- |
| -- |
Understanding Capability -- |
| -- |
What Does Your System Need to Achieve? -- |
| -- |
Don't Set Targets -- |
| -- |
Use Relative Goals with Caution -- |
| -- |
Challenge: Pull from the Future -- |
| -- |
End-to-End Flow -- |
| -- |
Eliminate Failure Demand -- |
| -- |
Map Value Demand -- |
| -- |
Find the Biggest Opportunity -- |
| -- |
Policy-Driven Waste -- |
| -- |
How Can Policies Cause Waste? -- |
| -- |
The Five Biggest Causes of Policy-Driven Waste -- |
| -- |
Complexity -- |
| -- |
Economies of Scale -- |
| -- |
Separating Decision Making from Work -- |
| -- |
Wishful Thinking -- |
| -- |
Technical Debt -- |
| -- |
Portrait: Product Champion, Take 1 -- |
| -- |
Customer-Facing Ideation -- |
| -- |
Technology-Facing Ideation -- |
| -- |
Your Shot -- |
| -- |
Technical Excellence -- |
| -- |
Facts, Fads, and Fallacies -- |
| -- |
Structured Programming -- |
| -- |
Top Down Programming -- |
| -- |
What Happened to Structured Programming? -- |
| -- |
Object-Oriented Programming -- |
| -- |
High-Level Languages -- |
| -- |
The Life Cycle Concept -- |
| -- |
Separation of Design from Implementation -- |
| -- |
Life Cycle Concept Considered Harmful -- |
| -- |
Evolutionary Development -- |
| -- |
Meanwhile, While No One Was Paying Attention -- |
| -- |
Why Did It Work? -- |
| -- |
Distraction -- |
| -- |
The Future of Agile -- |
| -- |
Essential Complexity -- |
| -- |
Divide and Conquer -- |
| -- |
The Internet Architecture Emerges -- |
| -- |
Low-Dependency Architecture -- |
| -- |
Conway's Law -- |
| -- |
Quality by Construction -- |
| -- |
Test-Driven Development -- |
| -- |
x Unit Frameworks -- |
| -- |
Acceptance Tests -- |
| -- |
Test Automation -- |
| -- |
Testing to Failure -- |
| -- |
Continuous Integration -- |
| -- |
How Often Is "Continuous"? -- |
| -- |
After Deployment -- |
| -- |
Code Clarity -- |
| -- |
Refactoring -- |
| -- |
Evolutionary Development -- |
| -- |
Ethnography -- |
| -- |
Collaborative Modeling -- |
| -- |
Quick Experimentation -- |
| -- |
Cycles of Discovery -- |
| -- |
Deep Expertise -- |
| -- |
Expertise Is Important -- |
| -- |
Developing Expertise -- |
| -- |
Deliberate Practice -- |
| -- |
The Ten-Year Rule -- |
| -- |
Retention -- |
| -- |
Standards -- |
| -- |
Code Reviews -- |
| -- |
Portrait: Competency Leader -- |
| -- |
Growing Technical Expertise -- |
| -- |
Your Shot -- |
| -- |
Reliable Delivery -- |
| -- |
Race to the Sky -- |
| -- |
How Did They Do It? -- |
| -- |
Team Design -- |
| -- |
Flow -- |
| -- |
Schedule -- |
| -- |
Decoupling -- |
| -- |
Logistics -- |
| -- |
Cash Flow Thinking -- |
| -- |
Proven Experience -- |
| -- |
Constraints Expose Risk -- |
| -- |
System Design -- |
| -- |
Design Loopbacks -- |
| -- |
Implementation Complexity -- |
| -- |
Three Ways to Reduce Schedule Complexity -- |
| -- |
Level Workflow -- |
| -- |
Small Batches -- |
| -- |
Iterations -- |
| -- |
Making Work Ready -- |
| -- |
Kanban -- |
| -- |
How Kanban Works -- |
| -- |
Iterations or Kanban? -- |
| -- |
Commitment -- |
| -- |
Teamwork -- |
| -- |
Batch Size -- |
| -- |
Cadence -- |
| -- |
Capacity -- |
| -- |
Iterations: Velocity -- |
| -- |
Kanban: Throughput -- |
| -- |
Pull Scheduling -- |
| -- |
Scheduling Medium-Sized Systems -- |
| -- |
Decouple -- |
| -- |
Scheduling Small, Frequent Requests -- |
| -- |
Arbitrate with Value -- |
| -- |
Limit Queues -- |
| -- |
Scheduling Larger Systems -- |
| -- |
Timebox-Don't Scopebox -- |
| -- |
Portfolio Management -- |
| -- |
Adaptive Control -- |
| -- |
Customer Feedback Every Iteration -- |
| -- |
Frequent Releases -- |
| -- |
Consumability -- |
| -- |
Escaped Defects -- |
| -- |
Customer Outcomes -- |
| -- |
Portrait: Product Champion, Take 2 -- |
| -- |
The Story of a Product Champion -- |
| -- |
February 2004, Harvard University -- |
| -- |
June 2004, Palo Alto -- |
| -- |
Fall 2006, Palo Alto -- |
| -- |
February 2007, Chicago -- |
| -- |
Summer 2007. Chicago -- |
| -- |
January 2008, New Hampshire -- |
| -- |
June 2008, Denver -- |
| -- |
November 2008, Chicago -- |
| -- |
Your Shot -- |
| -- |
Relentless Improvement -- |
| -- |
Sick Hospitals -- |
| -- |
The Checklist -- |
| -- |
No Work-arounds -- |
| -- |
No Ambiguity -- |
| -- |
Quick Experiments -- |
| -- |
Visualize Perfection -- |
| -- |
The Theoretical Limit -- |
| -- |
High-Velocity Organizations -- |
| -- |
Customer Focus -- |
| -- |
Establish a Baseline -- |
| -- |
Work Design -- |
| -- |
Output -- |
| -- |
Pathway -- |
| -- |
Connections -- |
| -- |
Test-Driven Handovers -- |
| -- |
Process Standards -- |
| -- |
Expose Problems -- |
| -- |
Go to the Workplace -- |
| -- |
Learn to Improve -- |
| -- |
The Goal Is Learning -- |
| -- |
Problem/Countermeasure Board -- |
| -- |
A3 Thinking -- |
| -- |
Pull-Based Authority -- |
| -- |
Responsibility Authority -- |
| -- |
Share the Knowledge -- |
| -- |
Portrait: Manager as Mentor -- |
| -- |
Your Shot -- |
| -- |
Great People -- |
| -- |
Cultural Assumptions -- |
| -- |
The Cultural Heritage of Management Practices -- |
| -- |
Agile Software Development -- |
| -- |
Lean Software Development -- |
| -- |
Company Culture -- |
| -- |
Knowledge Workers -- |
| -- |
Knowledge Worker Productivity -- |
| -- |
Results Are Nor the Point -- |
| -- |
The Norm of Reciprocity -- |
| -- |
Remuneration or Reciprocity? -- |
| -- |
Mutual Respect -- |
| -- |
Cross-Cultural Teams -- |
| -- |
The Value of Diversity -- |
| -- |
Self-Organizing Teams? -- |
| -- |
Pride of Workmanship -- |
| -- |
Purpose-Passion-Persistence-Pride -- |
| -- |
Portrait: Front-Line Leaders -- |
| -- |
Your Shot -- |
| -- |
Aligned Leaders -- |
| -- |
Agile@IBM -- |
| -- |
The Transformation -- |
| -- |
Stakeholder Involvement -- |
| -- |
An Early Experiment -- |
| -- |
Lessons Learned -- |
| -- |
From Theory to Practice -- |
| -- |
Focus on Customer Outcomes -- |
| -- |
Change the System -- |
| -- |
Create a Sense of Urgency -- |
| -- |
Governance -- |
| -- |
Beyond Budgeting -- |
| Miscellaneous information |
12. |
| Title |
Principles -- |
| -- |
What Is Productivity? -- |
| -- |
Alignment -- |
| -- |
Cause and Effect -- |
| -- |
Sustainability -- |
| -- |
Portrait: Leaders at All Levels -- |
| -- |
Leaders Provide Purpose -- |
| -- |
Leaders Set the Tone and Tempo -- |
| -- |
Leaders Make People Better -- |
| -- |
Leaders Create Space for Others to Succeed. |
| 588 ## - SOURCE OF DESCRIPTION NOTE |
|---|
| Source of description note |
Machine converted from AACR2 source record. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name entry element |
Management information systems. |
| 9 (RLIN) |
320358 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name entry element |
Computer software |
| General subdivision |
Development. |
| 9 (RLIN) |
315909 |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name entry element |
Organizational effectiveness. |
| 9 (RLIN) |
321742 |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Poppendieck, Thomas David, |
| Relator term |
author. |
| 9 (RLIN) |
269624 |
| 830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE |
|---|
| Uniform title |
Addison-Wesley signature series. |
| 9 (RLIN) |
1048681 |
| 907 ## - LOCAL DATA ELEMENT G, LDG (RLIN) |
|---|
| a |
.b11743426 |
| b |
21-03-18 |
| c |
27-10-15 |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) |
|---|
| Koha item type |
Book |
| 945 ## - LOCAL PROCESSING INFORMATION (OCLC) |
|---|
| a |
658.4038011 POP |
| g |
1 |
| i |
A451604B |
| j |
0 |
| l |
cmain |
| o |
- |
| p |
$74.75 |
| q |
- |
| r |
- |
| s |
- |
| t |
0 |
| u |
4 |
| v |
7 |
| w |
0 |
| x |
2 |
| y |
.i13061392 |
| z |
29-10-15 |
| 998 ## - LOCAL CONTROL INFORMATION (RLIN) |
|---|
| -- |
b |
| -- |
c |
| Operator's initials, OID (RLIN) |
06-04-16 |
| Cataloger's initials, CIN (RLIN) |
m |
| First date, FD (RLIN) |
a |
| -- |
eng |
| -- |
nju |
| -- |
0 |
