Rating:
Author: Mitch Lacey
ISBN : B007JWJVCA
New from $19.79
Format: PDF, EPUB
Posts about Download The Book Free The Scrum Field Guide: Practical Advice for Your First Year from mediafire, rapishare, and mirror link 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.
Direct download links available for Free The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series) [Kindle Edition]
- File Size: 5494 KB
- Print Length: 416 pages
- Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
- Publisher: Addison-Wesley Professional; 1 edition (March 12, 2012)
- Sold by: Amazon Digital Services, Inc.
- Language: English
- ASIN: B007JWJVCA
- Text-to-Speech: Enabled
X-Ray:
- Lending: Not Enabled
- Amazon Best Sellers Rank: #62,018 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #31
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Development
- #31
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Development
Free The Scrum Field Guide: Practical Advice for Your First Year
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:
-Contracting
-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.
-
Download Link 2