Recommendations based on "Radical Candor How to Get What You Want by Saying What You Mean"

Most managers fail. Some 70% of employees say they are dissatisfied with their line manager. A shocking 50% are labelled as incompetent, a disappointment or a wrong hire by their co-workers. But, what do we expect when over half new managers are given no training when they are promoted? Becoming a manager isn't a progression; it's an entirely new job. Penguin Expert Series: Managing People is a manual for managers who want to succeed in their new job, motivate and direct their teams and establish a working culture where everyone wants to do their best work. The book condenses Simon Birkenhead's decades of experience working as a team leader. He reveals; what makes a good manager, highlights common pitfalls to avoid, presents his tried and tested 'four-lever framework.' With strategies to activate motivation in your team, set goals and expectations, provide feedback and coaching to building a high-performance culture, and plenty of examples from across industries, this is everything first-time managers need to succeed and be the boss that everyone wants to work for.

The 10th-anniversary edition of the New York Times business bestseller-now updated with "Answers to Ten Questions People Ask"We attempt or avoid difficult conversations every day-whether dealing with an underperforming employee, disagreeing with a spouse, or negotiating with a client. From the Harvard Negotiation Project, the organization that brought you Getting to Yes, Difficult Conversations provides a step-by-step approach to having those tough conversations with less stress and more success. you'll learn how to:· Decipher the underlying structure of every difficult conversation· Start a conversation without defensiveness· Listen for the meaning of what is not said· Stay balanced in the face of attacks and accusations· Move from emotion to productive problem solving

How to Write Code You're Proud of . . . Every Single Day". . . [A] timely and humble reminder of the ever-increasing complexity of our programmatic world and how we owe it to the legacy of humankind--and to ourselves--to practice ethical development. Take your time reading Clean Craftsmanship. . . . Keep this book on your go-to bookshelf. Let this book be your old friend--your Uncle Bob, your guide--as you make your way through this world with curiosity and courage."--From the Foreword by Stacia Heimgartner Viscardi, CST & Agile MentorIn Clean Craftsmanship, the legendary Robert C. Martin ("Uncle Bob") has written the principles that define the profession--and the craft--of software development. Uncle Bob brings together the disciplines, standards, and ethics you need to deliver robust, effective code and to be proud of all the software you write.Robert Martin, the best-selling author of Clean Code, provides a pragmatic, technical, and prescriptive guide to the foundational disciplines of software craftsmanship. He discusses standards, showing how the world's expectations of developers often differ from their own and helping you bring the two in sync. Bob concludes with the ethics of the programming profession, describing the fundamental promises all developers should make to their colleagues, their users, and, above all, themselves.With Uncle Bob's insights, all programmers and their managers can consistently deliver code that builds trust instead of undermining it--trust among users and throughout societies that depend on software for their survival.Moving towards the "north star" of true software craftsmanship: the state of knowing how to program wellPractical, specific guidance for applying five core disciplines: test-driven development, refactoring, simple design,collaborative programming, and acceptance testsHow developers and teams can promote productivity, quality, and courageThe true meaning of integrity and teamwork among programmers, and ten specific commitments every software professional should makeRegister your book for convenient access to the book's companion videos, updates, and/or corrections as they become available. See inside book for details.

Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control. Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned. Fundamentals of XP include: Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system--several times a day. Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable. Why is XP so controversial? Some sacred cows don't make the cut in XP: Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XPprogrammers continue to make analysis and design decisions throughout development. Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code. You may love XP, or you may hate it, but "Extreme Programming Explained" will force you to take a fresh look at how you develop software. 0201616416B04062001

" Collaboration Explained is a deeply pragmatic book that helps agile practitioners understand and manage complex organizational and team dynamics. As an agile coach, I've found the combination of straightforward advice and colorful anecdotes to be invaluable in guiding and focusing interactions with my teams. Jean's wealth of experience is conveyed in a carefully struck balance of reference guides and prose, facilitating just-in-time learning in the agile spirit. All in all, a superb resource for building stronger teams that's fit for agile veterans and neophytes alike." -Arlen Bankston, Lean Agile Practice Manager, CC Pace "If Agile is the new 'what, ' then surely Collaboration is the new 'how.' There are many things I really like about Jean's new book. Right at the top of the list is that I don't have to make lists of ideas for collaboration and facilitation anymore. Jean has it all. Not only does she have those great ideas for meetings, retrospectives, and team decision-making that I need to remember, but the startling new and thought-provoking ideas are there too. And the stories, the stories, the stories! The best way to transfer wisdom. Thanks, Jean!" -Linda Rising, Independent Consultant The Hands-On Guide to Effective Collaboration in Agile Projects To succeed, an agile project demands outstanding collaboration among all its stakeholders. But great collaboration doesn't happen by itself; it must be carefully planned and facilitated throughout the entire project lifecycle. Collaboration Explained is the first book to bring together proven, start-to-finish techniques for ensuring effective collaboration in any agile software project. Since the early days of the agile movement, Jean Tabaka has been studying and promoting collaboration in agile environments. Drawing on her unsurpassed experience, she offers clear guidelines and easy-to-use collaboration templates for every significant project event: from iteration and release planning, through project chartering, all the way through post-project retrospectives. Tabaka's hands-on techniques are applicable to every leading agile methodology, from Extreme Programming and Scrum to Crystal Clear. Above all, they are practical: grounded in a powerful understanding of the technical, business, and human challenges you face as a project manager or development team member. Build collaborative software development cultures, leaders, and teams Prepare yourself to collaborate-and prepare your team Define clear roles for each participant in promoting collaboration Set your collaborative agenda Master tools for organizing collaboration more efficiently Run effective collaborative meetings-including brainstorming sessions Promote better small-group and pair-programming collaboration Get better information, and use it to make better decisions Use non-abusive conflict to drive positive outcomes Collaborate to estimate projects and schedules more accurately Strengthen collaboration across distributed, virtual teams Extend collaboration from individual projects to the entire development organization (c) Copyright Pearson Education. All rights reserved.

Lean Development and Agile Methods for Large-Scale Products: Key Thinking and Organizational Tools for Sustainable Competitive Success Increasingly, large product-development organizations are turning to lean thinking, agile principles and practices, and large-scale Scrum to sustainably and quickly deliver value and innovation. However, many groups have floundered in their practice-oriented adoptions. Why? Because without a deeper understanding of the thinking tools and profound organizational redesign needed, it is as though casting seeds on to an infertile field. Now, drawing on their long experience leading and guiding large-scale lean and agile adoptions for large, multisite, and offshore product development, and drawing on the best research for great team-based agile organizations, internationally recognized consultant and best-selling author Craig Larman and former leader of the agile transformation at Nokia Networks Bas Vodde share the key thinking and organizational tools needed to plant the seeds of product development success in a fertile lean and agile enterprise. Coverage includes Lean thinking and development combined with agile practices and methods Systems thinking Queuing theory and large-scale development processes Moving from single-function and component teams to stable cross-functional cross-component Scrum feature teams with end-to-end responsibility for features Organizational redesign to a lean and agile enterprise that delivers value fast Large-scale Scrum for multi-hundred-person product groups In a competitive environment that demands ever-faster cycle times and greater innovation, applied lean thinking and agile principles are becoming an urgent priority. Scaling Lean & Agile Development will help leaders create the foundation for their lean enterprise-and deliver on the significant benefits of agility. In addition to the foundation tools in this text, see the companion book Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum for complementary action tools.

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.

The Complete Guide to Avoiding and Fixing Common Rails 3 Code and Design Problems As developers worldwide have adopted the powerful Ruby on Rails web framework, many have fallen victim to common mistakes that reduce code quality, performance, reliability, stability, scalability, and maintainability. Rails™ AntiPatterns identifies these widespread Rails code and design problems, explains why they’re bad and why they happen—and shows exactly what to do instead. The book is organized into concise, modular chapters—each outlines a single common AntiPattern and offers detailed, cookbook-style code solutions that were previously difficult or impossible to find. Leading Rails developers Chad Pytel and Tammer Saleh also offer specific guidance for refactoring existing bad code or design to reflect sound object-oriented principles and established Rails best practices. With their help, developers, architects, and testers can dramatically improve new and existing applications, avoid future problems, and establish superior Rails coding standards throughout their organizations. This book will help you understand, avoid, and solve problems with Model layer code, from general object-oriented programming violations to complex SQL and excessive redundancy Domain modeling, including schema and database issues such as normalization and serialization View layer tools and conventions Controller-layer code, including RESTful code Service-related APIs, including timeouts, exceptions, backgrounding, and response codes Third-party code, including plug-ins and gems Testing, from test suites to test-driven development processes Scaling and deployment Database issues, including migrations and validations System design for “graceful degradation” in the real world

“Bernstein has become a guru to a peculiarly ’90s group: well-educated, Internet-powered people intent on investing well—and with minimal ‘help’ from professional Wall Street.”--Robert Barker, BusinessWeek William Bernstein is one of today’s most unlikely financial heroes. A practicing neurologist, he used his self-taught investment knowledge and research to build a popular investor’s website. Now, in the plain-spoken The Intelligent Asset Allocator, he shows independent investors how to build a diversified portfolio—without the help of a financial advisor. A breath of fresh air for investors tired of overly technical investment tomes, this book will help investors: Learn the risk/reward characteristics of various investment types Understand and apply portfolio theory for an improved risk/reward ratio Sharpen their focus, and take control of their investment programs William Bernstein runs a website—www.efficientfrontier.com—known for its quarterly journal of asset allocation and portfolio theory, Efficient Frontier.

“Our job as Scrum professionals is to continually improve our ability to use Scrum to deliver products and services that help customers achieve valuable outcomes. This book will help you to improve your ability to apply Scrum.”—From the Foreword by Ken Schwaber, co-author of ScrumMastering Professional Scrum is for anyone who wants to deliver increased value by using Scrum more effectively. Leading Scrum practitioners Stephanie Ockerman and Simon Reindl draw on years of Scrum training and coaching to help you return to first principles and apply Scrum with the professionalism required to achieve its transformative potential.The authors aim to help you focus on proven Scrum approaches for improving quality, getting and using fast feedback, and becoming more adaptable, instead of “going through the motions” and settling for only modest improvements.Whether you’re a Scrum Master, Development Team member, or Product Owner, you’ll find practical advice for facing challenges with transparency and courage, overcoming a wide array of common challenges, and continually improving your Scrum practice.Realistically assess your current Scrum practice, and identify areas for improvementRecognize what a great Scrum Team looks like and get thereFocus on “Done”—not “sort-of-Done” or “almost-Done”Measure and optimize the value delivered by every Product IncrementImprove the way you plan, develop, and growClear away wider organizational impediments to agility and professionalismOvercome common misconceptions that stand in the way of progressRegister your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.