Weinberg shows you exactly how to become a more effective consultant. He reveals specific techniques and strategies that really work.Through the use of vividly memorable rules, laws, and principles -- such as The Law of Raspberry Jam, The Potato Chip Principle, and Lessons from the Farm -- the author shows you how to-- price and market your services-- avoid traps and find alternative approaches-- keep ahead of your clients-- create a special "consultant's survival kit"-- trade improvement for perfection-- negotiate in difficult situations-- measure your effectiveness-- be yourselfYou will also find straightforward advice on marketing your services, including how to-- find clients-- get needed exposure-- set just-right fees-- gain trustThe Secrets of Consulting -- techniques, strategies, and first-hand experiences -- all that you'll need to set up, run, and be successful at your own consulting business.

    A pocket-sized overview of roles, artifacts and the sprint cycle, adapted from the bestseller The Elements of Scrum by Chris Sims & Hillary Louise Johnson

    

    The massive pressure on CIOs continues to increase as the opportunities to use technology in business become more prevalent and more competitive. As CIOs often find themselves at the center of business conflict, they must not only familiarize themselves with Machiavellian tactics as a defensive weapon, but also learn to use them as an offensive weapon in extreme situations so that they can increase IT’s contribution to their enterprises.As Italian political philosopher Niccolo Machiavelli implied, you're either predator or prey, and the animal you most resemble determines your position on the food chain. In The Wolf in CIO's Clothing Gartner analyst and author Tina Nunno expands on Machiavelli's metaphor, examining seven animal types and the leadership attributes of each. Nunno posits the wolf — a social animal with strong predatory instincts — as the ideal example of how a leader can adapt and thrive.Technology may be black and white, but successful leadership demands an ability to exist in the grey. Drawing on her experience with hundreds of CIOs, Nunno charts a viable way to master the Machiavellian principles of power, manipulation, love, and war. Through compelling case studies, her approach demonstrates how CIOs and IT leaders can adjust their leadership styles in extreme situations for their own success and that of their teams.

    Authentic knowledge body of Scrum is Scrum Guide. It is too dense to absorb without context and correlations. This book reveals Scrum as defined in 'The Scrum Guide 2016' with context and correlations using Active Learning technique. It is all-in-one guide for Professional Scrum Master (PSM 1) aspirants, with comprehensive Scrum material, tips, and 250+ practice questions.

    But one day she loses control and yells back. Terrified that she’ll be fired, she seeks out Isabel, the call center’s sage.      The advice she receives from her wise mentor changes her life:·         SODA (Stop. Observe. Decide. Act)—a sure-fire formula for remaining calm in any situation·         Unplugging—a centuries-old practice to reduce anxiety and promote creativity·         Aha!s—22 practical insights that become the framework for living a happy life      This modern-day fable shows us that the best way to reduce stress is to cultivate mindfulness. While we cannot control much of what happens, we can get better outcomes if we stop to see situations clearly and calmly.      This book serves as both a powerful resource for business professionals looking for practical, easy-to-use tools for dealing with difficult people and an inspirational tale for those who want better relationships and a happier life.

    Why? Too many organizations still view software development as just another production line. Too many developers feel that way, too--and they behave accordingly. In The Software Craftsman: Professionalism, Pragmatism, Pride, Sandro Mancuso offers a better and more fulfilling path. If you want to develop software with pride and professionalism; love what you do and do it with excellence; and build a career with autonomy, mastery, and purpose, it starts with the recognition that you are a craftsman. Once you embrace this powerful mindset, you can achieve unprecedented levels of technical excellence and customer satisfaction. Mancuso helped found the world's largest organization of software craftsmen; now, he shares what he's learned through inspiring examples and pragmatic advice you can use in your company, your projects, and your career. You will learn Why agile processes aren't enough and why craftsmanship is crucial to making them work How craftsmanship helps you build software right and helps clients in ways that go beyond code How and when to say "No" and how to provide creative alternatives when you do Why bad code happens to good developers and how to stop creating and justifying it How to make working with legacy code less painful and more productive How to be pragmatic--not dogmatic--about your practices and tools How to lead software craftsmen and attract them to your organization What to avoid when advertising positions, interviewing candidates, and hiring developers How developers and their managers can create a true culture of learning How to drive true technical change and overcome deep patterns of skepticism Sandro Mancuso has coded for startups, software houses, product companies, international consultancies, and investment banks. In October 2013, he cofounded Codurance, a consultancy based on Software Craftsmanship principles and values. His involvement with Software Craftsmanship began in 2010, when he founded the London Software Craftsmanship Community (LSCC), now the world's largest and most active Software Craftsmanship community, with more than two thousand craftsmen. For the past four years, he has inspired and helped developers to organize Software Craftsmanship communities throughout Europe, the United States, and the rest of the world.

    Through in-depth interviews and discussions, the common attributes of these elite project managers—from character and beliefs to organizational approaches—are uncovered and help to explain their achievements. Painstakingly researched, this guide offers key insights by providing multiple perspectives on the character makeup of the world’s most successful project managers.

    I learned about myself and learned lessons I will carry with me and reflect on for the rest of my life.”—John W. Fanning, Founding Chairman and CEO napster Inc.“An unusually nuanced view of high-performance cultures.” —Inc.Within each corporation are anywhere from a few to hundreds of separate tribes. In Tribal Leadership, Dave Logan, John King, and Halee Fischer-Wright demonstrate how these tribes develop—and show you how to assess them and lead them to maximize productivity and growth. A business management book like no other, Tribal Leadership is an essential tool to help managers and business leaders take better control of their organizations by utilizing the unique characteristics of the tribes that exist within.

    Casey had every reason to believe that his performance over the next two hours would determine the fate of his career, his financial future, and the company he had built from scratch."""How could my life have unraveled so quickly?" he wondered."In his latest page-turning work of business fiction, best-selling author Patrick Lencioni provides readers with another powerful and thought-provoking book, this one centered around a cure for the most painful yet underestimated problem of modern business: bad meetings. And what he suggests is both simple and revolutionary.Casey McDaniel, the founder and CEO of Yip Software, is in the midst of a problem he created, but one he doesn't know how to solve. And he doesn't know where or who to turn to for advice. His staff can't help him; they're as dumbfounded as he is by their tortuous meetings.Then an unlikely advisor, Will Peterson, enters Casey's world. When he proposes an unconventional, even radical, approach to solving the meeting problem, Casey is just desperate enough to listen.As in his other books, Lencioni provides a framework for his groundbreaking model, and makes it applicable to the real world. "Death by Meeting" is nothing short of a blueprint for leaders who want to eliminate waste and frustration among their teams, and create environments of engagement and passion.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    The book has three parts: Principles: Part one covers the leadership principles that PMs use to lead their team to overcome adversity. When your product fails to gain traction, when your team falls apart, or when your manager gives you tough feedback—these are all opportunities to learn principles that will help you succeed. Product development: Part two covers how PMs at Facebook, Amazon, and other top companies build products. We'll walk through the end-to-end product development process— from understanding the customer problem to identifying the right product to build to executing with your team to bring the product to market. Getting the job: Part three covers how you can land a PM job and reach the interview stage at the right company. We'll prep you for the three most common types of PM interviews— product sense, execution, and behavioral—with detailed frameworks and examples for each. Hear directly from product leaders at Airbnb, Amazon, Google, and more on: How to overcome challenging situations from a VP of Product at Amazon. How to build a great product roadmap from product leaders at LinkedIn and Airbnb. How Google, Airbnb, and other top companies evaluate PM candidates from leaders at those companies. How PMs can grow their career from a Director at Instagram and Twitter. Table of Contents1. PrinciplesTake OwnershipPrioritize and ExecuteStart with WhyFind the TruthBe Radically TransparentBe Honest with Yourself2. Product DevelopmentProduct Development LoopUnderstanding the Customer ProblemSelecting a Goal MetricMission, Vision, and StrategyBuilding a Product RoadmapDefining Product RequirementsGreat Project ManagementEffective CommunicationMaking Good Decisions3. Getting the JobPreparing for the TransitionMaking the TransitionFinding the Right CompanyAcing your PM InterviewsProduct Sense InterviewExecution InterviewBehavioral InterviewYour First 30 Days4. Product Leader Interviews

    What has been missing from the agile literature is a solid, practical book on the specifics of developing large projects in an agile way. Dean Leffingwell's book Scaling Software Agility fills this gap admirably. It offers a practical guide to large project issues such as architecture, requirements development, multi-level release planning, and team organization. Leffingwell's book is a necessary guide for large projects and large organizations making the transition to agile development." -Jim Highsmith, director, Agile Practice, Cutter Consortium, author of Agile Project Management "There's tension between building software fast and delivering software that lasts, between being ultra-responsive to changes in the market and maintaining a degree of stability. In his latest work, Scaling Software Agility, Dean Leffingwell shows how to achieve a pragmatic balance among these forces. Leffingwell's observations of the problem, his advice on the solution, and his description of the resulting best practices come from experience: he's been there, done that, and has seen what's worked." -Grady Booch, IBM Fellow Agile development practices, while still controversial in some circles, offer undeniable benefits: faster time to market, better responsiveness to changing customer requirements, and higher quality. However, agile practices have been defined and recommended primarily to small teams. In Scaling Software Agility, Dean Leffingwell describes how agile methods can be applied to enterprise-class development. Part I provides an overview of the most common and effective agile methods. Part II describes seven best practices of agility that natively scale to the enterprise level. Part III describes an additional set of seven organizational capabilities that companies can master to achieve the full benefits of software agility on an enterprise scale. This book is invaluable to software developers, testers and QA personnel, managers and team leads, as well as to executives of software organizations whose objective is to increase the quality and productivity of the software development process but who are faced with all the challenges of developing software on an enterprise scale. Foreword Preface Acknowledgments About the Author Part I: Overview of Software Agility Chapter 1: Introduction to Agile Methods Chapter 2: Why the Waterfall Model Doesn't Work Chapter 3: The Essence of XP Chapter 4: The Essence of Scrum Chapter 5: The Essence of RUP Chapter 6: Lean Software, DSDM, and FDD Chapter 7: The Essence of Agile Chapter 8: The Challenge of Scaling Agile Part II: Seven Agile Team Practices That Scale Chapter 9: The Define/Build/Test Component Team Chapter 10: Two Levels of Planning and Tracking Chapter 11: Mastering the Iteration Chapter 12: Smaller, More Frequent Releases Chapter 13: Concurrent Testing Chapter 14: Continuous Integration Chapter 15: Regular Reflection and Adaptation Part III: Creating the Agile Enterprise Chapter 16: Intentional Architecture Chapter 17: Lean Requirements at Scale: Vision, Roadmap, and Just-in-Time Elaboration Chapter 18: Systems of Systems and the Agile Release Train Chapter 19: Managing Highly Distributed Development Chapter 20: Impact on Customers and Operations Chapter 21: Changing the Organization Chapter 22: Measuring Business Performance Conclusion: Agility Works at Scale Bibliography Index

    You open the box and right on top is a quick-start guide. Being a novice, you follow the guide, and quickly get up and running. As you become more experienced, the other box contents address common advanced issues you'd face, like right-sizing teams, estimation, hitting deadlines, transitioning from Scrum or Waterfall, deploying components and services, and using Kanban within larger organizations.Real-world experience from a direct practitioner working on Xbox and Xbox.comA concise, pragmatic, and easy-to-read guide with clear, fresh, and hard-won guidanceUsing Kanban within larger organizations - how to deal with upper management, planning, and dependencies

    Executives set aggressive goals, so managers drive their teams to burnout trying to deliver. Or, employees seek connection and support, so managers focus on relationships . . . and fail to make the numbers. The fallout is stress, frustration, and disengagement, and not just among team members—two-thirds of managers report being disengaged.To succeed, managers cannot choose between results and relationships. They need both: They must get people to achieve while creating an environment that makes them truly want to. Winning Well offers managers a quick, practical action plan—complete with examples, stories, and online assessments. They will learn how to: Stamp out the corrosive win-at-all-costs mentality Focus on the game, not just the score Reinforce behaviors that produce results Sustain energy and momentum Correct poor performance without drama Build productive relationships Be the leader people want to work for Today’s hypercompetitive economy has created tense, overextended workplaces. Keep it productive, rewarding, and even fun with this one-stop success kit.