The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    In the late 1990s, it provided an optimistic model for public

    Is it time to become a manager? Tell your boss he’s a jerk? Join that startup? Author Michael Lopp recalls his own make-or-break moments with Silicon Valley giants such as Apple, Netscape, and Symantec in Being Geek -- an insightful and entertaining book that will help you make better career decisions.With more than 40 standalone stories, Lopp walks through a complete job life cycle, starting with the job interview and ending with the realization that it might be time to find another gig. Many books teach you how to interview for a job or how to manage a project successfully, but only this book helps you handle the baffling circumstances you may encounter throughout your career.Decide what you're worth with the chapter on "The Business"Determine the nature of the miracle your CEO wants with "The Impossible"Give effective presentations with "How Not to Throw Up"Handle liars and people with devious agendas with "Managing Werewolves"Realize when you should be looking for a new gig with "The Itch"

    This book isn't about that - it's about everything else. As such, there's very little code inside, meaning everyone from PHP hackers to hardcore embedded C programmers will get a lot out of it.This book covers 10 topics crucial to being an amazing developer:Focus on Delivering ResultsFix Bugs Efficiently and CleanlyAdd Features with EaseDeal With Technical Debt and SlopPlay Well With OthersMake Technical DecisionsBootstrap a Greenfield SystemLearn to WriteInterview Potential Co-WorkersLead a Team

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    You will be able to look over the shoulder of major coding and design experts to see problems through their eyes.This is not simply another design patterns book, or another software engineering treatise on the right and wrong way to do things. The authors think aloud as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to break rules. Beautiful Code is an opportunity for master coders to tell their story. All author royalties will be donated to Amnesty International.

    But which claims are verifiable, and which are merely wishful thinking? In this book, leading thinkers such as Steve McConnell, Barry Boehm, and Barbara Kitchenham offer essays that uncover the truth and unmask myths commonly held among the software development community. Their insights may surprise you.Are some programmers really ten times more productive than others?Does writing tests first help you develop better code faster?Can code metrics predict the number of bugs in a piece of software?Do design patterns actually make better software?What effect does personality have on pair programming?What matters more: how far apart people are geographically, or how far apart they are in the org chart?Contributors include:Jorge Aranda Tom Ball Victor R. Basili Andrew Begel Christian Bird Barry Boehm Marcelo Cataldo Steven Clarke Jason Cohen Robert DeLine Madeline Diep Hakan Erdogmus Michael Godfrey Mark Guzdial Jo E. Hannay Ahmed E. Hassan Israel Herraiz Kim Sebastian Herzig Cory Kapser Barbara Kitchenham Andrew Ko Lucas Layman Steve McConnell Tim Menzies Gail Murphy Nachi Nagappan Thomas J. Ostrand Dewayne Perry Marian Petre Lutz Prechelt Rahul Premraj Forrest Shull Beth Simon Diomidis Spinellis Neil Thomas Walter Tichy Burak Turhan Elaine J. Weyuker Michele A. Whitecraft Laurie Williams Wendy M. Williams Andreas Zeller Thomas Zimmermann

    Mastering large-scale software delivery will define the economic landscape of the 21st century, just as mass production defined the landscape in the 20th. Unfortunately, business and technology leaders outside of the tech giants are woefully ill-equipped to solve the problems posed by digital transformation. A new approach is needed.In Project to Product, value stream network pioneer and technology leader Dr. Mik Kersten introduces the Flow Framework. This new way of building an infrastructure for innovation will change the way enterprises think about software delivery, enabling every organization the opportunity to win a portion of the $18.5 trillion (IDC) that will be created annually through better software delivery.Project to Product provides leaders the missing framework needed to create the technology equivalent of an advanced manufacturing line, across thousands of IT professionals, and enables optimizing value creation across the entire organization. This book is ideal for C-suite leadership and IT management at every level.

     The Workbook's easy-to-use worksheets make efficient planning simple and practical and supports your success in three ways:Reflection: Think about your approach to leadership and become more conscious about how well you engage in each of the Practices.Application Apply the Practices and commitments to all your projects.Implications Record what you've learned about yourself, your team, your organization, and your project. Develop your leadership potential with The Leadership Challenge Workbook!

    Lavishly illustrated with Dilbert strips, these hilarious essays on incompetent bosses, management fads, bewildering technological changes and so much more, will make anyone who has ever worked in an office laugh out loud in recognition. The Dilbert Principle: The most ineffective workers will be systematically moved to the place where they can do the least damage -- management.Since 1989, Scott Adams has been illustrating this principle each day, lampooning the corporate world through Dilbert, his enormously popular comic strip. In Dilbert, the potato-shaped, abuse-absorbing hero of the strip, Adams has given voice to the millions of Americans buffeted by the many adversities of the workplace.Now he takes the next step, attacking corporate culture head-on in this lighthearted series of essays. Packed with more than 100 hilarious cartoons, these 25 chapters explore the zeitgeist of ever-changing management trends, overbearing egos, management incompetence, bottomless bureaucracies, petrifying performance reviews, three-hour meetings, the confusion of the information superhighway and more. With sharp eyes, and an even sharper wit, Adams exposes -- and skewers -- the bizarre absurdities of everyday corporate life. Readers will be convinced that he must be spying on their bosses, The Dilbert Principle rings so true!

    The author does not purport to be inventing strategy in this book or to be revealing the secrets of Japanese business and strategic planning. Rather, he is exploring with the reader the ways in which the strategist must think, the key principles and thought patterns that real-world strategists have used to move their companies forward in Japan and throughout the world. He explores the relationship of the Strategic Triangle formed by the company, the customer, and the competition and shows how these factors must be the basis for all strategic thinking and planning.

    In Enterprise Architecture as Strategy: Creating a Foundation for Business Execution, authors Jeanne W. Ross, Peter Weill, and David C. Robertson show you how.The key? Make tough decisions about which processes you must execute well, then implement the IT systems needed to digitize those processes. Citing numerous companies worldwide, the authors show how constructing the right enterprise architecture enhances profitability and time to market, improves strategy execution, and even lowers IT costs. Though clear, engaging explanation, they demonstrate how to define your operating model—your vision of how your firm will survive and grow—and implement it through your enterprise architecture. Their counterintuitive but vital message: when it comes to executing your strategy, your enterprise architecture may matter far more than your strategy itself.

    There are currently a significant number of books on creating, documenting, and implementing software architecture, but precious few resources have addressed how to build a software architecture that aligns with a customer's overall business goals. In this new book, Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions. This book helps technologists grasp the business ramifications of their decisions, and provides business-oriented software professionals (e.g. sales people and marketers) with better knowledge of how robust software can be built and maintained.

     The only route to success is to know yourself, inside and out. Through the framework of Professor Gardner’s multiple intelligence theory, you find your strengths, unique ways to enhance them, and ultimately use them to catapult yourself to success and the life that you’ve always wanted to live. All my life changes started when I understood that I was making a living from rat race jobs I hated and best case I was mediocre in them. By finding my main intelligence type I started doing something I love and I’m good in. Today I am a bestselling author and interpersonal skills coach and created the life I wanted. Now my goal is to help you create the life you want. I particularly understand what drives success and I also know precisely what's holding you back, and I can help. Finding what you were born for empowers you: - Learn about 8+1 types of intelligence and the research proven methods how to improve each of them - How to find and bring out the maximum of your innate strengths - How to make your vocation your profession - How can you divide lifelong success to small and easy day to day tasks You will also learn: - How to build higher quality of life - How to get out of the 9-5 rat race - How to introduce your passion in your life without the risk of losing your livelihood - How to make the best decisions for short and long term success What improvements will you experience if you follow the advice in this book? - You will live a well-balanced, full life - Wake up every day grateful and excited to see what lies ahead. - Know what – when and how to improve in you for maximum results - Be the role model instead of looking for one If you want to discover your strengths, make them your passion and live a meaningful life… Scroll up and click BUY NOW to step onto the road of success and happiness.

    From choosing the right cells to designing a battery pack and building it yourself, this book includes all the steps for building safe, effective custom lithium battery packs.