|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
よく一緒に購入されている商品
商品の説明
内容説明
Praise for Agile Estimating and Planning
"Traditional, deterministic approaches to planning and estimating simply don't cut it on the slippery slopes of today's dynamic, change-driven projects. Mike Cohn's breakthrough book gives us not only the philosophy, but also the guidelines and a proven set of tools that we need to succeed in planning, estimating, and scheduling projects with a high uncertainty factor. At the same time, the author never loses sight of the need to deliver business value to the customer each step of the way."
Doug DeCarlo, author of eXtreme Project Management: Using Leadership, Principles and Tools to Deliver Value in the Face of Volatility (Jossey-Bass, 2004)
"We know how to build predictive plans and manage them. But building plans that only estimate the future and then embrace change, challenge most of our training and skills. In Agile Estimating and Planning, Mike Cohn once again fills a hole in the Agile practices, this time by showing us a workable approach to Agile estimating and planning. Mike delves into the nooks and crannies of the subject and anticipates many of the questions and nuances of this topic. Students of Agile processes will recognize that this book is truly about agility, bridging many of the practices between Scrum and ExtremeProgramming."
Ken Schwaber, Scrum evangelist, Agile Alliance cofounder, and signatory to the Agile Manifesto
"In Agile Estimating and Planning, Mike Cohn has, for the first time, brought together most everything that the Agile community has learned about the subject. The book is clear, well organized, and a pleasant and valuable read. It goes into all the necessary detail, and at the same time keeps the reader's burden low. We can dig in as deeply as we need to, without too much detail before we need it. The book really brings together everything we have learned about Agile estimation and planning over the past decade. It will serve its readers well."
Ron Jeffries, www.XProgramming.com, author of Extreme Programming Installed (Addison-Wesley, 2001) and Extreme Programming Adventures in C# (Microsoft Press, 2004)
"Agile Estimating and Planning provides a view of planning that's balanced between theory and practice, and it is supported by enough concrete experiences to lend it credibility. I particularly like the quote 'planning is a quest for value.' It points to a new, more positive attitude toward planning that goes beyond the 'necessary evil' view that I sometimes hold."
Kent Beck, author of Extreme Programming Explained, Second Edition (Addison-Wesley, 2005)
"Up-front planning is still the most critical part of software development. Agile software development requires Agile planning techniques. This book shows you how to employ Agile planning in a succinct, practical, and easy-to-follow manner."
Adam Rogers, Ultimate Software
"Mike does a great follow-up to User Stories Applied by continuing to provide Agile teams with the practical approaches and techniques to increase agility. In this book, Mike provides time-proven and well-tested methods for being successful with the multiple levels of planning and estimating required by Agile. This book is the first to detail the disciplines of Agile estimating and planning, in ways that rival my 1980 civil engineering texts on CPM Planning and Estimating."
Ryan Martens, President and Founder, Rally Software Development Corporation
"With insight and clarity, Mike Cohn shows how to effectively produce software of high business value. With Agile estimation and planning, you focus effort where it really counts, and continue to do so as circumstances change."
Rick Mugridge, Rimu Research Ltd., and lead author, Fit for Developing Software (Prentice Hall, 2005)
"Finally! The groundbreaking book my clients have been clamoring for! Agile Estimating and Planning demystifies the process of defining, driving, and delivering great software that matters to the business. Mike's clarity, insight, and experience leap out through every page of this book, offering an approach that is relevant and immediately useful to all members of an Agile project."
Kert D. Peterson, President, Enterprise Agile Group, LLC
"This isn't yet another generic book on Agile software development. Agile Estimating and Planning fills a gap left by most of the other books and gives you important, practical, down-to-earth techniques needed to be successful on Agile development projects."
Steve Tockey, Principal Consultant, Construx Software
"Estimation, planning, and tracking is a trinity. If you don't do one of them, you don't need the other two. This book provides very practical knowledge for estimation, planning, prioritizing, and tracking. It should be compulsory subject matter for project managers and their teams, even if they hesitate to call themselves Agile."
Niels Malotaux, Project Coach
"Effective planning is an important, but often misunderstood, part of any successful Agile project. With Agile Estimating and Planning, Mike Cohn has given us a definitive guide to a wide range of Agile estimating and planning practices. With his clear and practical style, Mike not only explains how to successfully get started planning an Agile project, but also provides a wealth of tips and advice for improving any team's Agile planning process. This book is a must-read for managers, coaches, and members of Agile teams."
Paul Hodgetts, Agile coach and CEO, Agile Logic
"Mike's writing style captures the essence of agility-just the right amount of information to bring clarity to the reader. This book provides an excellent guide for all Agile practitioners, both seasoned and novice."
Robert Holler, President and CEO, VersionOne, LLC
"It is as if Mike took the distilled knowledge regarding planning and estimation of a great Agile developer (which he is) and laid out all he knows in an easily understandable manner. More importantly, he has a great mix of concepts with real-world examples finished off with a case study so the reader can relate the information to their own situation. Unless you are already an expert Agile planner and estimator, this book is for you."
Alan Shalloway, CEO, Senior Consultant, Net Objectives, and coauthor of Design Patterns Explained, Second Edition (Addison-Wesley, 2005)
"Although I had plenty of XP experience before trying out Mike Cohn's Agile planning practices, the effectiveness of the practical and proven techniques in this book blew me away! The book recognizes that people, not tools or processes, produce great software, and that teams benefit most by learning about their project and their product as they go. The examples in the book are concrete, easily grasped, and simply reek of common sense. This book will help teams (whether Agile or not) deliver more value, more often, and have fun doing it! Whether you're a manager or a programmer, a tester or a CEO, part of an Agile team, or just looking for a way to stamp out chaos and death marches, this book will guide you."
Lisa Crispin, coauthor of Testing Extreme Programming (Addison-Wesley, 2003)
"Mike Cohn does an excellent job demonstrating how an Agile approach can address issues of risk and uncertainty in order to provide more meaningful estimates and plans for software projects."
Todd Little, Senior Development Manager, Landmark Graphics
"Mike Cohn explains his approach to Agile planning, and shows how 'critical chain' thinking can be used to effectively buffer both schedule and features. As with User Stories Applied, this book is easy to read and grounded in real-world experience."
Bill Wake, author of Refactoring Workbook (Addison-Wesley, 2003)
"Mike brings this book to life with real-world examples that help reveal how and why an Agile approach works for planning software development projects. This book has great breadth, ranging from the fundamentals of release planning to advanced topics such as financial aspects of prioritization. I can see this book becoming an invaluable aid to Agile project managers, as it provides a wealth of practical tips such as how to set iteration length and boot-strap velocity, and communicate progress."
Rachel Davies, Independent Consultant
"There has been a need for a solid, pragmatic book on the long-term vision of an Agile Project for project managers. Agile Estimating and Planning addresses this need. It's not theorythis book contains project-tested practices that have been used on Agile projects. As Mike's test subjects, we applied these practices to the development of video games (one of the most unpredictable project environments you can imagine) with success."
Clinton Keith, Chief Technical Officer, High Moon Studios
"When I first heard Mike Cohn speak, I was impressed by a rare combination of qualities: deep experience and understanding in modern iterative and Agile methods; a drive to find and validate easy, high-impact solutions beyond the status quo of traditional (usually ineffective) methods; and the passion and clarity of a natural coach. These qualities are evident in this wonderful, practical guide. I estimate you won't be disappointed in studying and applying his advice."
Craig Larman, Chief Scientist, Valtech, and author of Applying UML and Patterns, Third Edition (Prentice Hall, 2005) and Agile and Iterative Development (Addison-Wesley, 2004)
"Agile Estimating and Planning is a critical guide on how to successfully provide value to customers of IT services. This book is filled with clear examples that are essentialfrom project team...
著者について
Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. With more than twenty years of experience, Mike has been a technology executive in companies ranging from start-ups to Fortune 40s, and is a founding member of the Agile Alliance. He frequently contributes to industry-related magazines and presents regularly at conferences. He is the author of User Stories Applied (Addison-Wesley, 2004).
登録情報
|
この商品を見た後に買っているのは？
カスタマーレビュー
最も参考になったカスタマーレビュー
形式:ペーパーバック
Craig Larmanの"Agile and Iterative Development"を読んで、アジャイルに入れ込んでしまった私が、次に探したアジャイル本が本書です。期待以上の内容で、具体的にアジャイル開発を適用しようと思っている方々には、絶対にお薦めです。
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
61件のカスタマーレビュー
201 人中、169人の方が、｢このレビューが参考になった｣と投票しています。
Draw the Line
2006/1/30
形式:ペーパーバック|Amazonが確認した購入
A 5 star review just doesn't mean anything anymore. There are some good ideas in this book, but large stretches of this book are just absurd. This thing reads like homework that was finished on the bus (you can almost see the bumps in the road). The structure of the book is completely haphazard. One minute, we are talking about doing estimates. The next minute we are trying to figure out how a project will pay for itself, then, it's on to how to split up stories that got too big. I was waiting for a sidebar with a recipe for a great chiffon cake. At the end of the chapter on estimating value, the author recommends another book and says that's where his content came from (citational plagiarism is called 'plugging,' Youngster). Then, the chapter on splitting stories made me laugh out loud in places. Things like 'split stories along data lines,' or 'split stories along priority lines' or one of the funniest 'split it along CRUD lines.' Come on.
The good part of this book is the one chapter on estimation and discussion of things like using Fibonacci for bucketing of estimates into story points, the importance of seeing estimates as relative, and the idea of doing planning poker. In short: again, it's an article that was turned into a book by a set of expansion techniques that are astounding for not being illegal, let alone questionable. And all this inside a fortress of testimonials that makes Fort Knox look lightly defended.
The good part of this book is the one chapter on estimation and discussion of things like using Fibonacci for bucketing of estimates into story points, the importance of seeing estimates as relative, and the idea of doing planning poker. In short: again, it's an article that was turned into a book by a set of expansion techniques that are astounding for not being illegal, let alone questionable. And all this inside a fortress of testimonials that makes Fort Knox look lightly defended.
27 人中、24人の方が、｢このレビューが参考になった｣と投票しています。
The Planning Approach that Refreshes
2006/2/12
形式:ペーパーバック
Better planning, as Mary Poppendieck (author of "Lean Software Development") points out, results in a higher standard of living for the individual, for the team, and for the organization. With "Agile Estimating and Planning", Mike Cohn delivers a beautifully pragmatic approach for pushing us into the notion that this higher standard of living is completely attainable for our software development projects in this lifetime.
Mike's earlier book, "User Stories Applied" has been one of my most cited books when working with teams new to agile software development. Understanding the usefulness of the story concept as the base unit of function delivery has put these new teams in a good steady stride for being realiably realistic about their work delivery toward feature completion.
With Mike's "AE&P", I now have a fully referenceable guide that moves the team story planning pragmatics to the next level: bringing multiple planning approaches to bear at multiple levels for multiple measures of software feature acceptance and completion. In his usual style, Mike delivers his guidance with wonderfully accessible non-software analogies. For example, "How long is a football game?" and "How long will it take me to move my pile of dirt?" for understanding the distinction between effort (or ideal hours/days)and duration (total calendar hours/days). These simple mental models set the stage for ruthlessly correcting the many misunderstood atrributes of planning and its life partner estimating. Having shattered the myths of task-based Gantt Charts, PERT charts, and Work Breakdown Structures as completely repeatable prediction models for planning and estimation, Mike rebuilds the planning toolbox with practices that truly work. He buoys his practices (such as Planning Poker and frequent replanning) with the de rigueur reinforcements of appropriate metrics (e.g. how many tests did we complete in the last iteration, how many story points did we complete in our worst iteration, how are we tracking today with our estimates of what is left to do) that really guide teams in how to steadily improve their planning acumen.
Because my passion in agile software development has focused more and more on the importance of participatory decision-making in order to make planning commitments stick, I am particularly grateful that Mike sets a high collaborative bar with regard to how team's must work in order to create effective and actionable plans. Guidance on collaboration, high visibility, and continuous inspection are woven into all the practices in Mike's book, start to finish.
If I can leave you with only one piece of advice from "AE&P", take Mike's "Dozen Guidelines for Agile Estimating and Planning" (Chapter 22) and nail them to your team's door. In fact, nail them to your business partner or product manager's door. If you allowed me a second piece of advice: read through his excellent case study that follows in Chapter 23. And then, if you forgave me one final piece of advice: be prepared to start enjoying your new standard of living.
Mike's earlier book, "User Stories Applied" has been one of my most cited books when working with teams new to agile software development. Understanding the usefulness of the story concept as the base unit of function delivery has put these new teams in a good steady stride for being realiably realistic about their work delivery toward feature completion.
With Mike's "AE&P", I now have a fully referenceable guide that moves the team story planning pragmatics to the next level: bringing multiple planning approaches to bear at multiple levels for multiple measures of software feature acceptance and completion. In his usual style, Mike delivers his guidance with wonderfully accessible non-software analogies. For example, "How long is a football game?" and "How long will it take me to move my pile of dirt?" for understanding the distinction between effort (or ideal hours/days)and duration (total calendar hours/days). These simple mental models set the stage for ruthlessly correcting the many misunderstood atrributes of planning and its life partner estimating. Having shattered the myths of task-based Gantt Charts, PERT charts, and Work Breakdown Structures as completely repeatable prediction models for planning and estimation, Mike rebuilds the planning toolbox with practices that truly work. He buoys his practices (such as Planning Poker and frequent replanning) with the de rigueur reinforcements of appropriate metrics (e.g. how many tests did we complete in the last iteration, how many story points did we complete in our worst iteration, how are we tracking today with our estimates of what is left to do) that really guide teams in how to steadily improve their planning acumen.
Because my passion in agile software development has focused more and more on the importance of participatory decision-making in order to make planning commitments stick, I am particularly grateful that Mike sets a high collaborative bar with regard to how team's must work in order to create effective and actionable plans. Guidance on collaboration, high visibility, and continuous inspection are woven into all the practices in Mike's book, start to finish.
If I can leave you with only one piece of advice from "AE&P", take Mike's "Dozen Guidelines for Agile Estimating and Planning" (Chapter 22) and nail them to your team's door. In fact, nail them to your business partner or product manager's door. If you allowed me a second piece of advice: read through his excellent case study that follows in Chapter 23. And then, if you forgave me one final piece of advice: be prepared to start enjoying your new standard of living.
23 人中、20人の方が、｢このレビューが参考になった｣と投票しています。
A Pseudo-Quantitative Method for Estimation
2008/2/25
形式:ペーパーバック
This book presents a pseudo-quantitative method for estimation for so-called agile development. Cohn suggests subjectively estimating relative size of user stories on some arbitrary scale (within one order of magnitude) in a round-table approach called Planning Poker. Getting input from key stakeholders is a good strategy....not only does it develop buy-in, it sets expectations and clearly defines the scope. However, caution must be taken when using Planning Poker; these roundrobin techniques are often used as a way of influencing a group to agree on a predetermined conclusion. In addition the team must guard against "Groupthink," where individuals intentionally conform to what they think will be the ultimate conclusion of the group as a whole. During this Poker process, Cohn suggests estimating relative sizes of user stories on a Fibonacci sequence scale (1, 2, 3, 5, and 8). The problem with using this--or any numeric scale--is that there is an inherent implication that the effort required to implement each User Story is proportionate to the scale. (I.e. a user story estimated at 8 Story Points will require 4x the effort of a User Story estimated at 2 Story Points). In estimation false precision is the enemy of accuracy. Any computational methods applied to these Story Points (such as the calculation of velocity, essentially a delivery rate, in terms of story points implemented per unit time) is much less valid than the number imply. Agile development is much more adaptive than waterfall and even more so than iterative. With its Timeboxed deliveries on the order of weeks (rather than months) and responsive nature with respect to requirements change, I can see how predicting this type of fluid development would certainly qualify as nontrivial.
With that said, the advantage of relative size, according to Bozoki, is that very early on, estimates of relative sizes are more accurate than estimates of absolute sizes. Cohn's methods also leverage another fact of life: the Law of Large Numbers (LLN). The LLN provides a tendency for errors inherent in a bunch of small estimates (like User Stories) to cancel each other out to a limited extent.
My primary concern with this method is that we have an qualitative method disguised as a quantitative method with out adequate consideration of estimate uncertainty/error propagation.
With that said, the advantage of relative size, according to Bozoki, is that very early on, estimates of relative sizes are more accurate than estimates of absolute sizes. Cohn's methods also leverage another fact of life: the Law of Large Numbers (LLN). The LLN provides a tendency for errors inherent in a bunch of small estimates (like User Stories) to cancel each other out to a limited extent.
My primary concern with this method is that we have an qualitative method disguised as a quantitative method with out adequate consideration of estimate uncertainty/error propagation.
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
リストマニア
|
|
関連商品を探す
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
