In weniger als einer Minute können Sie mit dem Lesen von The Scrum Field Guide: Practical Advice for Your First Year auf Ihrem Kindle beginnen. Sie haben noch keinen Kindle? Hier kaufen oder mit einer unserer kostenlosen Kindle Lese-Apps sofort zu lesen anfangen.

An Ihren Kindle oder ein anderes Gerät senden


Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Keine Abbildung vorhanden

The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series) [Kindle Edition]

Mitch Lacey
5.0 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)

Kindle-Preis: EUR 22,30 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

Kostenlose Kindle-Leseanwendung Jeder kann Kindle Bücher lesen  selbst ohne ein Kindle-Gerät  mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.

Geben Sie Ihre E-Mail-Adresse oder Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 22,30  
Taschenbuch EUR 25,95  



Thousands of IT professionals are being asked to make Scrum succeed in their organizations–including many who weren’t involved in the decision to adopt it. If you’re one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You’ll learn how to gain “quick wins” that build support, and then use the flexibility of Scrum to maximize value creation across the entire process.


In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn’t) be modified. Coverage includes


  • Getting teams on board, and bringing new team members aboard after you’ve started
  • Creating a “definition of done” for the team and organization
  • Implementing the strong technical practices that are indispensable for agile success
  • Balancing predictability and adaptability in release planning
  • Keeping defects in check
  • Running productive daily standup meetings
  • Keeping people engaged with pair programming
  • Managing culture clashes on Scrum teams
  • Performing “emergency procedures” to get sprints back on track
  • Establishing a pace your team can truly sustain
  • Accurately costing projects, and measuring the value they deliver
  • Documenting Scrum projects effectively
  • Prioritizing and estimating large backlogs
  • Integrating outsourced and offshored components


Packed with real-world examples from Lacey’s own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.


Über den Autor und weitere Mitwirkende

Mitch Lacey has been an agile practitioner and consultant and is the founder of Mitch Lacey & Associates, Inc., a software consulting and training firm. Mitch helps teams and companies realize gains in efficiency by adopting agile principles and practices such as Scrum and Extreme Programming. Mitch cut his agile teeth at Microsoft Corporation working on a variety of projects, sometimes as the product owner, other times as the ScrumMaster. Today, with more than 16 years of experience under his belt, Mitch works as an agile trainer and coach. He also continues to develop his craft by experimenting and practicing with project teams at many different organizations.Mitch is a Certified Scrum Trainer (CST) and a PMI Project Management Professional (PMP). He is a frequent speaker at conferences worldwide; has served on the board of the Scrum Alliance and the Agile Alliance; and chaired the Agile 2012 conference.


  • Format: Kindle Edition
  • Dateigröße: 5295 KB
  • Seitenzahl der Print-Ausgabe: 416 Seiten
  • Gleichzeitige Verwendung von Geräten: Bis zu 5 Geräte gleichzeitig, je nach vom Verlag festgelegter Grenze
  • Verlag: Addison-Wesley Professional; Auflage: 1 (12. März 2012)
  • Verkauf durch: Amazon Media EU S.à r.l.
  • Sprache: Englisch
  • ISBN-10: 0321670345
  • ISBN-13: 978-0321670342
  • Text-to-Speech (Vorlesemodus): Aktiviert
  • X-Ray:
  • Word Wise: Nicht aktiviert
  • Durchschnittliche Kundenbewertung: 5.0 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
  • Amazon Bestseller-Rang: #206.224 Bezahlt in Kindle-Shop (Siehe Top 100 Bezahlt in Kindle-Shop)

  •  Ist der Verkauf dieses Produkts für Sie nicht akzeptabel?

Mehr über den Autor

Mitch Lacey is an agile practitioner and trainer. He is also the founder of Mitch Lacey & Associates, Inc., a software consulting and training firm. Mitch specializes in helping companies realize gains in efficiency by adopting agile principles and practices such as Scrum and extreme programming.

Mitch was a formally trained program manager before adding agile to his project tool belt. He first developed agile skills at Microsoft Corporation, where he successfully released core enterprise services for Windows Live. Mitch's first agile team at Microsoft was coached by Ward Cunningham, Jim Newkirk, and David Anderson. Mitch continued practicing at Microsoft by working as a product owner or ScrumMaster on a variety of projects. He also helped teams throughout the organization adopt agile practices. He continues to develop his craft by experimenting and practicing with project teams he works on today.

Mitch is a Certified Scrum Trainer (CST), a PMI Project Management Professional (PMP) and PMI Agile Certified Professional (ACP). Mitch shares his experience in project and client management through Certified ScrumMaster courses, agile coaching engagements, conference presentations, blogs, and white papers. Mitch works with companies across the world, from Austria to Columbia, California to Florida, Portugal to Turkey, and just about everywhere in between.

Mitch has presented at a variety of conferences worldwide, is the conference chair for Agile 2012, and is on the board of directors of the Agile Alliance and served on the board of directors for the Scrum Alliance from July 2010 through December 2011.


4 Sterne
3 Sterne
2 Sterne
1 Sterne
5.0 von 5 Sternen
5.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A helpful guide not only for the first year 25. April 2012
Von Karschtl
We've started with Scrum in 2009 and are way past our first year. Nevertheless I found this book quite informative on how to meet challenges. And be sure - we still have them after all this time, they just keep changing their outfit.

I did read the book in order, but you really don't have to - just scan the TOC and pick out the topics that currently interest you. After illustrating the topic with a story from the real word, Lacey always continues with presenting the modela and keys to success. This way you become swiftly familiar with the pattern of the book, which makes it a good reference book also for the future if you want to go back to a certain technique or model you read of some time before.

Although my team (I'm a Scrum Master) doesn't face every problem described in this book, I read at least the story of each chapter because I found them quite enjoyable. Mostly I was then so curious about the proposed solution that I read the models and keys to success as well. Even if you don't need to fix the problem described in your team, you pick up bits and pieces here & there that can be quite helpful in your daily work as a Scrum Master.

I see Scrum Masters as the target group to benefit the most from this book, but would also like it if management or team members might read it to raise their awareness and understanding for certain issues. To hear it from a 'Scrum professional' might make it easier for us 'normal ppl' to argue with them.
When buying this book, please consider the name: it's a 'field' guide that presents common problematic issues occuring when doing Scrum. It's not a book on what Scrum and all it entails is in theory (although there is an appendix explaining the roles, artifacts and meetings in Scrum).
Lesen Sie weiter... ›
War diese Rezension für Sie hilfreich?
1 von 1 Kunden fanden die folgende Rezension hilfreich
Format:Kindle Edition
Nachdem ich bei Mitch Lacey ein Scrum Master Training absolviert habe, besorgte ich mir das Buch. Auf den ersten Blick ist es ein sehr umfangreiches Buch dass auf dem zweiten Blick jedoch sehr gut strukturiert ist.

Die Kindle Edition des Buches ist gut gelungen und ich habe es daher jeden Tag mit. Es ersetzt vollständig die manuellen Recherchen im Internet über Details von Scrum und "Was gehe ich wie an". Mitch gliedert die Kapitel in eine Story die dem Scrum Anfänger die Ausgangssituation beschreibt und das zu lösende Problem näher bringt. Danach folgt relativ Kompakt der Inhalt des jeweiligen Kapitels.

Die elektronische Version gewinnt insbesondere durch eine sehr effiziente Referenzierung zwischen den Kapiteln und einem gelungen Index, der auch für Non-Native Speakers sehr gut zu verwenden ist.

Die Inhalte - abseits der Stories - sind kurz und prägnant formuliert und bringen die Dinge auf den Punkt: "Mach es auf diese Weise und es wird funktionieren!". Die verwenden Grafiken sind sparsam und gut geeignet, weiterverwendet zu werden.

Es ist ein gelungenes Buch für Einsteiger (Buch bitte von vorne lesen) und erfahrene Scrum-User (sehr gut als Referenz zu nutzen) und bekommt meine Sterne für:
- gelungenen Gesamt-Aufbau
- Guter Aufbau in den Kapiteln (Story, Model)
- Ausgezeichnete Umsetzung auf dem Kindle
- Brachbarer Index und funktionierende Referenzen zwischen den Kapitel
- Anwendbarkeit in der Praxis
War diese Rezension für Sie hilfreich?
5.0 von 5 Sternen Einfach zu lesen, enthält praktische Tipps 8. November 2013
Ich hatte das Glück, das Buch nach einem von Mitch gehaltenen ScrumMaster-Training zu bekommen. Vielleicht gefällt manchen nicht so sehr, dass jedes Kapitel eine einleitende Geschichte enthält. Ich fand für das Anwenden der Tipps auf mein Team allerdings sehr hilfreich, dass der eigentlichen Lektion mit einer einfachen, verständlichen Geschichte ein Kontext gegeben wird. Speziell für jene, die mit Scrum gerade anfangen oder in ihrer ScrumMaster-Rolle neu sind, wird es dadurch leichter, ähnliche Situationen zu erkennen. Mehr als ein Jahr danach schaue ich immer noch oft und gerne in das Buch - nun nicht mehr, um die Geschichten zu lesen, sondern die Tipps und Erklärungen selbst. Auf jeden Fall ein großes "Dankeschön!" an Mitch für dieses Buch...
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf (beta) 4.9 von 5 Sternen  121 Rezensionen
14 von 15 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Must read for beginning and seasoned Scrum practitioners 26. März 2012
Von Bill Ramos - Veröffentlicht auf
I would recommend Mitch's book to anyone or team getting started with Scrum or as a refresher for practicing Scrum teams. The reading style of telling a story, discussing the model, identifying keys to success, and references for each chapter is a refreshing technique for understanding why elements of the Scrum model are important while making it easy to go back for future reference.

Here are some of the nuggets that I picked out.
- Adding a fourth question for people to answer at the daily standup meeting - on a scale of 1-10, how confident are you that we will accomplish the goals of this sprint?
- Contract strategies for Scrum based development efforts - especially around change control - if a customer adds a new story, they need to subtract a story or set of stories of equal story points.
- Decomposing stories into tasks with an example of going too far. I would have liked to seen a treatment on how to deal with predecessor tasks for the sprint.
- Best practices on running the sprint review and retrospective meetings.
- Dealing with special considerations and challenges for offshore development .
- Creating end-to-end user scenarios for sprint objectives to demonstrate software that is ready to ship.

Something that I would have liked to have seen in the book is how to manage multiple projects with Scrum and how to deal with scarce "team consultant" resources who can't be full time and may be asked to work on 3 or more projects during the same sprint cycle. Mitch points out the caution, but didn't provide a solution other than they need to be flexible. Multi-project release planning is always a challenge with shared resources.

Overall, this is a must read for beginning and seasoned Scrum practitioners.
9 von 10 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen A very practical approach to rescuing a Scrum implementation. 13. Juni 2012
Von Shane Willerton - Veröffentlicht auf
The Scrum Field Guide should not be your resource for learning and/or beginning to implement Scrum. It is the book you should turn to when you need to rescue your Scrum implementation. This is a practical approach to the more common obstacles that a Scrum implementation will encounter. The title of the first chapter sums it up succinctly: Scrum: Simple, Not Easy.

Scrum is the project management portion of Agile development. At a generic level, Scrum gives management the tools to monitor and track the progress of the favorite flavor of Agile development whether XP, TDD, etc. The Scrum Field Guide is geared mainly towards Scrum Masters, core team members or managers wanting to put their project back on track.

Every chapter can stand-alone and be read in any order. Each chapter begins with a story to help the reader draw parallels between the topic that the chapter addresses and the difficulties the reader is facing in their environment. Often, the symptoms of the different challenges can hide the root cause. From how to get recalcitrant core team members on board with using Scrum to recover Sprint Retrospectives turned gripe sessions, this book covers it all. The chapters are short in terms of page length because they are meant to offer ready-made and practical advice on common issues with the topic at hand rather than offer a detailed examination of each aspect of implementing Scrum.

Purchase this book when you get back from Scrum training or when you buy the book on how to implement Scrum. Put it on your shelf and refer to it when Scrum gets hard or just doesn't seem to work as advertised. This book will not teach you how to implement Scrum, it will help you save your implementation. Scrum's simple, but simple is not always easy!
8 von 9 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Great practical, hands-on book for people adopting Scrum and XP 23. März 2012
Von Tiago Andrade e Silva - Veröffentlicht auf
Great story format, easy to read, smart, practical advice.

I purchased this book because I attended one of Mitch's classes in Portugal a couple years ago, when he was working on it. I was in my first year of Scrum and XP at the time (his target market) and boy, do I wish I had this book then. I still purchased it and found a lot of new things. Some of my favorites are:
-How to handle documentation
-Definition of done
-How to justify having a ScrumMaster
-Engineering practices

Contracting. Mitch provides two models for the reader to consider when working with customers, either internal or external. While the ideas may sound crazy, they are not. I'm eager to try these models in the real world.

Documentation. This is always a battle. Mitch makes a good case for how, when and most importantly, why to document. It's not just a blanket "document everything" approach, nor is it the common "agile means no documentation" stuff that everyone seems to say at one point in their life. Instead it's a way to look at documentation, historically, and think about the right time to do it. He never says don't do it, or do it all - he says be smart about it, understand why you do it, and understand your customer. This is one of my favorite chapters.

Definition of done. There is a lot of writing on the Internet on this topic, but this is the first time I've seen something written where it actually walks a team through with an established technique on HOW to build a definition of done, how to use it and how to communicate it to customers and stakeholders. I let a friend borrow the book just for this section so he could use this chapter.

Justifying the ScrumMaster. I'm used to hear people (customers and project stakeholders) say "can't someone just be the product owner and the scrummaster? How hard can it be?" Well, Mitch provides a financial model that should make any customer drool when they understand how much impact a truly dedicated ScrumMaster can have on a team. It's a simple model to follow and I'll be showing this to many people the next time I'm told "no ScrumMasters allowed on this project".

Engineering practices. I am so glad he talked about this. I saw many Scrum implementations fail because they don't do the engineering practices, they just "do scrum so everything will be better" - which is not the case. The engineering practices he discusses are, in my option, key to doing Scrum. He talks about ways to introduce them gently and shows the benefits they will receive.

One thing to consider. This book does not dive into the basic details of Scrum. There is an appendix in the back that covers the basics, but it assumes you have done
some homework, read something about Scrum and XP and are looking at ways to get "over the roadblocks" so you can have a successful Scrum and XP implementation. This book is full of practical, pragmatic advice, and you won't see a lot of theory. Everything is practice/experience based, which is something I liked in Mitch since we first met.
3 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The Road Less Traveled 8. April 2012
Von Scott Densmore - Veröffentlicht auf
I have had the pleasure of knowing Mitch and reading his book. If you are new to SCRUM or starting another project using this methodology, this book is for you. If you always wish you had a field guide to help when working through your project, this is it. It takes some of the best practices to help guide you to a successful project.

No matter how many projects I go through, I always seem to pick up something new that rolls into my next project. Sometimes I remember them all, sometimes I forget and then think how much better the project would have been if I had only done something different. This book is like my little notebook of all those things that I can keep with me at all times.

The best part of the book is the way Mitch puts all these practices into light through the stories he tells. I am sure that when you read them, you will be saying, "been there, done that, got the T-Shirt".

Get this book. Carry it with you. Write in it. Use it to mold your process to be successful.
2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A Good Primer on Scrum, and easy way to get into it. 21. Dezember 2012
Von Bradley Ouellette - Veröffentlicht auf
A fun read, mixing entertaining stories with practical advice.

Mitch came to work and gave a talk on using scrum, while presenting, he advertised his book, it sounded interesting, and he offered anyone at the talk a free copy, so I read through it. If you go to his talk it's more in depth than what he can get through in a one day class. It still appears directed at the beginner user of Scrum, with many examples and solutions to common problems that will come up to new groups moving to scrum.

I liked how he presented the book as a collection of "What Not to do" stories, and then how to solve the problem they got themselves into. The stories often seem exaggerated, to make a point, but I fully believe they are all based on real events, and I can see many people falling unbeknownst to a similar situation in real life. For example, one of the stories describes a scrum team that has team member that works as the scrum master, the product owner, and tries to get work done on the team. I could easily see someone trying to do two of those roles.

The book is written to be read either from front to back, or as a reference guide skipping to the section that is relevant at the time. As you read through there are brief descriptions when he references something in another section, but usually it builds up such that you shouldn't have to skip to that section just to finish reading what your currently on.

He makes a lot of claims for how much good scrum and Extreme programming can do for your organization, but I like that he backed up all his claims with actual research. Quoting research papers where they tested how much of a performance degradation peer programming causes compared to how many fewer bugs, the code will produce. He also is including his real world experience, but you don't have to just take his word for it.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Erster Beitrag:
Eingabe des Log-ins

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen

Ähnliche Artikel finden