Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results
David J. Anderson
- 出版商: Prentice Hall
- 出版日期: 2003-09-27
- 定價: $1,820
- 售價: 5.0 折 $910
- 語言: 英文
- 頁數: 352
- 裝訂: Paperback
- ISBN: 0131424602
- ISBN-13: 9780131424609
-
相關分類:
Agile Software、軟體工程
立即出貨(限量) (庫存=1)
買這商品的人也買了...
-
$980$774 -
$299$254 -
$480$379 -
$580$568 -
$880$695 -
$780CMMI: Guidelines for Process Integration and Product Improvement (Harcover)
-
$590$466 -
$750$675 -
$560$504 -
$780$663 -
$480$379 -
$750$593 -
$490$417 -
$199$179 -
$1,078Operating System Principles, 7/e(IE) (美國版ISBN:0471694665-Operating System Concepts, 7/e) (平裝)
-
$1,050$1,029 -
$780$702 -
$650$507 -
$680$578 -
$880$695 -
$780$663 -
$680$537 -
$450$356 -
$780$616 -
$720$569
相關主題
商品描述
"This book does a good job of describing the methods employed at Sprintpcs.com ... over 250 people practicing Feature Driven Development and reporting their progress to me at the monthly operations review."
--Scott B. Relf, Chief Marketing Officer, Sprint PCS"A tremendous contribution to the literature in the field. This should be required reading for all development teams going forward."
--John F. Yuzdepski, VP & GM, Openwave SystemsA breakthrough approach to managing agile software developmentAgile methods might just be the alternative to outsourcing. However, agile development must scale in scope and discipline to be acceptable in the boardrooms of the Fortune 1000. In Agile Management for Software Engineering, David J. Anderson shows managers how to apply management science to gain the full business benefits of agility through application of the focused approach taught by Eli Goldratt in his Theory of Constraints.
Whether you're using XP, Scrum, FDD, or another agile approach, you'll learn how to develop management discipline for all phases of the engineering process, implement realistic financial and production metrics, and focus on building software that delivers maximum customer value and outstanding business results.Coverage includes:
- Making the business case for agile methods: practical tools and disciplines
- How to choose an agile method for your next project
- Breakthrough application of Critical Chain Project Management and constraint-driven control of the flow of value
- Defines the four new roles for the agile manager in software projects--and competitive IT organizations
Whether you're a development manager, project manager, team leader, or senior IT executive, this book will help you achieve all four of your most urgent challenges: lower cost, faster delivery, improved quality, and focused alignment with the business.
Table of Contents
Foreword.
Introduction.
Acknowledgements.SECTION I. AGILE MANAGEMENT.
1. Theories for Agile Management.
The Theory of Constraints. Just-in-Time Inventory. Quality. Lean Production. Six Sigma. Comparison of Theories. Scientific Proof for Agile Management. Empirical Versus Defined Processes. Convergent Versus Divergent Processes. Chaos Theory and Uncertainty. Systems Thinking and Learning Organizations. Emergence. Summary.2. Management Accounting for Systems.
A General System. Detail Complexity Versus Systems Complexity. Throughput Accounting for General Systems. A System of Software Development. A More Complex Software Development System. The System Goal. Financial Metrics for General Business Systems. Financial Metrics for Software Development Systems. Predicting the Future. Framing the Problem. Understanding Software Production in the Value Chain. Throughput Accounting Versus Cost Accounting. Summary.3. TOC in Software Production.
TOC's Five Basic Steps. Identify and Exploit Constraints. Perishable Requirements. Idleness Might Breed Contempt. Elevating a Constraint. Focus of Investment. Is the 8-Hour Day the Best Choice of System Constraint? Summary.4. Dealing with Uncertainty.
The Five Constraints of Software Development. Aggregation Reduces Uncertainty. Summary.5. Software Production Metrics.
Choosing Metrics. Agile Software Production Metrics. Traditional Software Production Metrics. Measuring Inventory in the Software Production System. Expressions of Inventory. Measuring Production Quantity. Lead Time. OE per Unit. Summary.6. Agile Project Management.
Traditional Versus RAD Model for Project Management. Task Planning and Effort Tracking. The Project Manager's New Work. Summary.7. Agile Project Planning.
The Project Buffer. Logical Collections of Inventory. The Critical Path and Parallel Paths. Early Start. Late Start. Feeding Buffers. Buffer Usage. Agile Project Tracking Metrics. Resource Constraints. Critical Chain Versus Critical Path. Summary.8. The Agile Manager's New Work.
New Roles for Agile Managers. Development Manager Role. The Program or Release Manager Role. Product Manager Role. Project Manager Role. Roles Versus Positions.9. Agile Development Management.
The Role of the Development Manager. Identifying Flow. Identifying a Bottleneck. The True Cost of a Bottleneck. Recovering and Stretching Software Production Constraints. The True Cost of Poor Quality. Regression Effects. Improve Quality in Front of a Bottleneck. How Batch Sizes Affect Flow. Monitoring Cumulative Flow. Visual Control. Summary.10. Software Resource Planning.
Manufacturing Resource Planning (MRP). Drum Beat. Planning Release of Requirements into the System. Summary.11. An Agile Maturity Model.
A New Maturity Model. Summary.12. Setting the Governing Rules.
Allow Adaptive Behavior to Emerge. The Role of the Agile Executive. Reinertsen's Three Tiers of Control. The Process Improvement Problem. The Problem with Production Rate Metrics. Governing Rules as Maturity Increases. Governing Rules for Managers. Governing Rules for Engineers. Team Measurements.13. Staffing Decisions.
Turnover. Loss of Throughput on a Constraint. Understanding the System Constraint is Essential. Outsource Decisions.14. Operations Review.
Purpose. Attendees. Timing. Information Rather Than Data. Summary.15. Agile Management in the IT Department.
Corporate IT's Value-Added Contribution. Learning from Financial Metrics. A More Profitable Corporate IT Department. Summary.16. Agile Product Management.
Sales and Throughput. Learning Is Not Restricted to Engineering. Management Accounting for Product Development. Throughput Accounting for Software Product Development. Appropriateness of the Time-Based Throughput Model. Cost Accounting for Software Product Development. Throughput Versus Cost Models. Making On-Going Investment. Product Mix. Managing the Scope Constraint. Product Mix When Revenue Is the Goal. Product Mix and the Effect on Investment. Product Mix, Risk, and Delay and the Effect on Operating Expense. Summary.17. Financial Metrics for Software Services.
Defining a Software Service. Service Business Economics. Determining Throughput for Software Services. Operating Expense for Services. Net Profit for Services. Return on Investment for Services. Attributing a Value to a Release. Profit and ROI by Service Release. Product Mix. Dealing with Uncertainty.18. The Business Benefit of Agile Methods.
The Principles of Agile Methods. More Than Agility. Making Profitable Development Happen.SECTION II. A SURVEY OF METHODS.
19. Production Metrics for Traditional Methods.
SDLC. Unified Development Process.20. Financial Metrics in Traditional Methods.
Inventory. Investment. Operating Expense. Throughput. Net Profit in Structured Methods. Return on Investment in Structured Methods. Accounting for Change.21. Production Metrics in FDD.
Overview of Feature Driven Development (FDD). Feature Definition. Agile Management Theory and FDD. Process Steps and FDD. Estimating OE for an FDD Project. The Modeling Rule of Thumb. Level of Effort Estimation in FDD. Formulae for Success.22. Project Management with FDD.
Self-Organizing Construction within Planned Assembly. Feature Sets. Build Batches. User Interface Feature Sets. Subject Areas. The Feature Lifecycle. Process Control in FDD. Estimates Versus Agreed Function. Scheduling an FDD Project. Scheduling Subject Areas and Feature Sets. FDD Workflow. FDD Knowledge Management System and Visual Control. Executive Management Metrics in FDD.23. FDD Process Elements Explained.
Exploiting Engineering Resources. The File Access Constraint—Class Ownership. The Developer Resource Constraint—Feature Teams and the Surgical Team. The Setup Time Constraint—Chief Programmer Work Packages. Batch Size. The Scope Constraint—Prioritized Feature Lists. The Time Constraint and Buffers. The Budget Constraint—Inventory Cap and Buffer. The Test Bottleneck. Advanced Modeling Techniques. Inventory Management in FDD. Morning Roll Call. How FDD Improves the S-Curve Effect. The Time Constraint Revisited. The Local Safety Problem. Exploiting Heroic Effort.24. Financial Metrics in FDD.
Inventory in FDD. Investment in FDD. Operating Expense in FDD. Throughput in FDD. Value-Added in FDD. Return on Investment in FDD. Accounting for Change. Accounting for Rework. Avoid Double-Counting.25. Production Metrics in Extreme Programming.
Metrics in XP. Raw Material. Inventory. Tasks. Throughput. Production Rate. Inventory Tracking. Lead Time. Process Step Time. Inventory Cap. Investment. Risk Philosophy. Testing. Pipelining. Refactoring. Metrics for Up-Management in XP.26. XP Process Elements Explained.
Assessing User Stories. Prioritizing Stories. Option Theory. The Planning Game. Continuous Integration. Integration Testing. Pair Programming. Stand-Up Meeting. Unit Testing. Collective Ownership. Refactoring. 40-Hour Week. On-Site Customer. Generalists. Elimination Versus Protection, Subordination, and Elevation.27. Financial Metrics in XP.
Inventory in XP. Investment in XP. Operating Expense in XP. Throughput in XP. Net Profit in XP. Return on Investment in XP. Accounting for Change. Accounting for Rework. The Cost of Change Curve.28. Production Metrics in Scrum.
Background. Raw Material. Inventory. Throughput. Production Rate. Metrics. Sprint Planning and Project Management. Inventory Tracking. Lead Time. Process Step Time. No Expediting. Inventory Cap. Investment. Risk Philosophy. Testing. Pipelining. Refactoring. Metrics for Up-Management in Scrum.29. Scrum Process Elements Explained.
The Scrum Master. The Product Backlog. The 30-Day Sprint. Release. The Sprint Goal Commitment. The Scrum Meeting. Team Size. Team Composition. Working Environment. The Sprint Review. Engineering Practices.30. RAD Process Elements Explained.
Principles of RAD. Inventory Cap. Lead Time. Operating Expense. Limits of RAD Methods.SECTION III. COMPARISON OF METHODS.
31. Devil's Advocacy.
Traditional Metrics Versus Agile Principles. Specialists Versus Generalists. Adding More People Makes Projects Later.32. States of Control and Reducing Variation.
The Ideal State. The Threshold State. The Edge of Chaos State. Chaos. Comprehending the Known Universe. Improving Analysis and Modeling Maturity. Improving the Process Maturity. FDD Focuses on Variance as Well as Quality and Inventory. XP Focuses on Quality and Short Lead Times. Comparison of Method Focus. Seek Process Maturity.33. Comparison of Production Metrics.
FDD. Extreme Programming. Scrum. Traditional Methods—Function Points. Traditional Methods—UDP. Summary.34. Applicability of Agile Methods.
Dividing up the Process Space. What is Agility? Scale Versus Ability to Expedite. Statistical Process Control and Agile Methods. What Does This Mean? Transferable Quality Improvement. Summary.Index.
商品描述(中文翻譯)
摘要:
這本書很好地描述了Sprintpcs.com所使用的方法...超過250人實踐功能驅動開發並在每月運營評估中向我報告他們的進展。-Sprint PCS首席營銷官Scott B. Relf
這是對該領域文獻的巨大貢獻。所有開發團隊都應該閱讀這本書。-Openwave Systems副總裁兼總經理John F. Yuzdepski
管理敏捷軟件開發的突破性方法
敏捷方法可能是外包的替代方案。然而,敏捷開發必須在範圍和紀律上擴展,以在財富1000強的董事會中獲得認可。在《敏捷軟件工程管理》一書中,David J. Anderson向管理者展示如何應用管理科學,通過應用Eli Goldratt在其制約理論中教授的專注方法,獲得敏捷的全部業務效益。
無論您使用XP、Scrum、FDD還是其他敏捷方法,您都將學習如何為工程過程的所有階段開發管理紀律,實施現實的財務和生產指標,並專注於構建能夠提供最大客戶價值和優秀業務結果的軟件。內容包括:
- 為敏捷方法提出商業案例:實用工具和紀律
- 如何為下一個項目選擇敏捷方法
- 突破性應用關鍵鏈專案管理和基於制約的價值流控制
- 定義敏捷經理在軟件項目和競爭性IT組織中的四個新角色
無論您是開發經理、項目經理、團隊領導還是高級IT執行官,本書將幫助您實現四個最迫切的挑戰:降低成本、更快交付、提高質量和與業務的專注對齊。
目錄:
前言
引言
致謝
第一部分:敏捷管理
1. 敏捷管理的理論
2. 系統的管理會計
3. 軟件生產中的制約理論
4. 應對不確定性
(以下省略)