So why should larger, more established companies take notice? Because they have everything to gain when they examine and adopt the strategies, tools, and attitudes of these smaller competitors. The Lean Enterprise presents a groundbreaking design for revolutionizing larger organizations, one that draws on the ingenious tenets and practices espoused by the startup community. The guidelines in this book will help companies shake the lethargy, bureaucracy, and power struggles that plague large organizations and hold them back from true innovation.At the heart of this resource is a comprehensive, practical approach based on methods, timetables, compensation, financial investment, and case studies that reveal the startup mentality. Respected thought leaders in lean startup methodologies, the authors cover successful enterprise development, development innovation labs, corporate venture arms, and acquisition and integration of startups.- Essential reading for entrepreneurs, product managers, executives and directors in Forbes 2000 organizations, and board members- Presents the tools and methodologies large businesses need to compete with a new generation of highly-empowered entrepreneurs- Covers lean startup culture and principles and identifies the behaviors that arestunting growth at large enterprises- Offers a comprehensive, practical approach for developing exciting products and services and opening vast new marketsDon't be mystified by the success of startups. Master the methods of this new generation of entrepreneurs and compete on a level playing field.

    Thank you for your feedback and patience.From Andrew Warner:I first interviewed Paul Graham after I heard something shocking from Alexis Ohanian, a founder whose company was funded by Graham's Y Combinator. Alexis came to Mixergy to tell the story of how he launched and sold Reddit.If you're a founder, you know the kind of problems that founders have, right? Figuring out what product to create, how to build it, how to get users to try it, etc.Well Alexis didn't seem to have those problems, or at least they weren't as challenging for him as they were for most of the other 600 entrepreneurs I interviewed on Mixergy.Why? Because Paul Graham helped him launch his business.How did Graham make Reddit's launch easier and more successful than other companies' founding? How did he do the same for hundreds of other startups? And, more importantly, what can you learn from his experiences to grow your business?The book you're holding has those answers.Use what you're about to learn to build your successful startup. After you do, I hope you'll let me interview you so other founders can learn from your experience, the way you're about to benefit from Graham's.About Hyperink, the publisher:Hyperink is the easiest way for anyone to publish a beautiful, high-quality book.We work closely with subject matter experts to create each eBook. We cover topics ranging from higher education to job recruiting, from Android apps marketing to barefoot running.If you have interesting knowledge that people are willing to pay for, especially if you've already produced content on the topic, please reach out to us! There's no writing required and it's a unique opportunity to build your own brand and earn royalties.

    Old-style system administrators may be disappearing in the face of automation and cloud computing, but operations have become more significant than ever. As this O'Reilly Radar Report explains, we're moving into a more complex arrangement known as "DevOps."Mike Loukides, O'Reilly's VP of Content Strategy, provides an incisive look into this new world of operations, where IT specialists are becoming part of the development team. In an environment with thousands of servers, these specialists now write the code that maintains the infrastructure. Even applications that run in the cloud have to be resilient and fault tolerant, need to be monitored, and must adjust to huge swings in load. That was underscored by Amazon's EBS outage last year.From the discussions at O'Reilly's Velocity Conference, it's evident that many operations specialists are quickly adapting to the DevOps reality. But as a whole, the industry has just scratched the surface. This report tells you why.

    Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly. This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers. The Art of Agile Development gives you clear answers to questions such as:How can we adopt agile development? Do we really need to pair program? What metrics should we report? What if I can't get my customer to participate? How much documentation should we write? When do we design and architect? As a non-developer, how should I work with my agile team? Where is my product roadmap? How does QA fit in? The book teaches you how to adopt XP practices, describes each practice in detail, then discusses principles that will allow you to modify XP and create your own agile method. In particular, this book tackles the difficult aspects of agile development: the need for cooperation and trust among team members. Whether you're currently part of an agile team, working with an agile team, or interested in agile development, this book provides the practical tips you need to start practicing agile development. As your experience grows, the book will grow with you, providing exercises and information that will teach you first to understand the rules of agile development, break them, and ultimately abandon rules altogether as you master the art of agile development. "Jim Shore and Shane Warden expertly explain the practices and benefits of Extreme Programming. They offer advice from their real-world experiences in leading teams. They answer questions about the practices and show contraindications - ways that a practice may be mis-applied. They offer alternatives you can try if there are impediments to applying a practice, such as the lack of an on-site customer. --Ken Pugh, Author of Jolt Award Winner, Prefactoring "I will leave a copy of this book with every team I visit." --Brian Marick, Exampler Consulting

    To grow professionally, you also need soft skills and effective learning techniques. Honing those skills is what this book is all about. Authors Dave Hoover and Adewale Oshineye have cataloged dozens of behavior patterns to help you perfect essential aspects of your craft. Compiled from years of research, many interviews, and feedback from O'Reilly's online forum, these patterns address difficult situations that programmers, administrators, and DBAs face every day. And it's not just about financial success. Apprenticeship Patterns also approaches software development as a means to personal fulfillment. Discover how this book can help you make the best of both your life and your career. Solutions to some common obstacles that this book explores in-depth include:Burned out at work? "Nurture Your Passion" by finding a pet project to rediscover the joy of problem solving.Feeling overwhelmed by new information? Re-explore familiar territory by building something you've built before, then use "Retreat into Competence" to move forward again.Stuck in your learning? Seek a team of experienced and talented developers with whom you can "Be the Worst" for a while. "Brilliant stuff! Reading this book was like being in a time machine that pulled me back to those key learning moments in my career as a professional software developer and, instead of having to learn best practices the hard way, I had a guru sitting on my shoulder guiding me every step towards master craftsmanship. I'll certainly be recommending this book to clients. I wish I had this book 14 years ago!" -Russ Miles, CEO, OpenCredo

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    Today, Rails developers and architects need better ways to interface with legacy systems, move into the cloud, and scale to handle higher volumes and greater complexity. In Service-Oriented Design with Ruby and Rails Paul Dix introduces a powerful, services-based design approach geared toward overcoming all these challenges. Using Dix's techniques, readers can leverage the full benefits of both Ruby and Rails, while overcoming the difficulties of working with larger codebases and teams. Dix demonstrates how to integrate multiple components within an enterprise application stack; create services that can easily grow and connect; and design systems that are easier to maintain and upgrade. Key concepts are explained with detailed Ruby code built using open source libraries such as ActiveRecord, Sinatra, Nokogiri, and Typhoeus. The book concludes with coverage of security, scaling, messaging, and interfacing with third-party services. Service-Oriented Design with Ruby and Rails will help you Build highly scalable, Ruby-based service architectures that operate smoothly in the cloud or with legacy systems Scale Rails systems to handle more requests, larger development teams, and more complex code bases Master new best practices for designing and creating services in Ruby Use Ruby to glue together services written in any language Use Ruby libraries to build and consume RESTful Web services Use Ruby JSON parsers to quickly represent resources from HTTP services Write lightweight, well-designed API wrappers around internal or external services Discover powerful non-Rails frameworks that simplify Ruby service implementation Implement standards-based enterprise messaging with Advanced Message Queuing Protocol (AMQP) Optimize performance with load balancing and caching Provide for security and authentication

    With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you can apply to all kinds of projects.A few of the 97 things you should know:"Code in the Language of the Domain" by Dan North"Write Tests for People" by Gerard Meszaros"Convenience Is Not an -ility" by Gregor Hohpe"Know Your IDE" by Heinz Kabutz"A Message to the Future" by Linda Rising"The Boy Scout Rule" by Robert C. Martin (Uncle Bob)"Beware the Share" by Udi Dahan

    Fully updated with the 2009 practice guidelines, this book will take you through every step of a project - from planning and establishing roles to closing and reviewing - offering practical and easy-to-understand advice on using PRINCE2. It also shows how to use the method when approaching the key concerns of project management, including setting up effective controls, managing project risk, managing quality and controlling change. PRINCE2 allows you to divide your project into manageable chunks, so you can make realistic plans and know when resources will be needed. PRINCE2 For Dummies, 2009 Edition provides you with a comprehensive guide to its systems, procedures and language so you can run efficient and successful projects.PRINCE2 For Dummies, 2009 Edition includes: Part I: How PRINCE Can Help You - Chapter 1: So What's a Project Method and Why Do I Need to Use One? - Chapter 2: Outlining the Structure of PRINCE2 - Chapter 3: Getting Real Power from PRINCE2Part II: Working Through Your Project - Chapter 4: Checking the Idea Before You Start - Chapter 5: Planning the Whole Project: Initiation - Chapter 6: Preparing for a Stage in the Project - Chapter 7: Controlling a Stage - Chapter 8: Building the Deliverables - the Work of the Teams - Chapter 9: Finishing the Project - Chapter 10: Running Effective Project BoardsPart III: Help with PRINCE Project Management - Chapter 11: Producing and Updating the Business Case - Chapter 12: Deciding Roles and Responsibilities - Chapter 13: Managing Project Quality - Chapter 14: Planning the Project, Stages, and Work Packages - Chapter 15: Managing Project Risk - Chapter 16: Controlling Change and Controlling Versions - Chapter 17: Monitoring Progress and Setting Up Effective ControlsPart IV: The Part of Tens - Chapter 18: Ten Ways to Make PRINCE Work Well - Chapter 19: Ten Tips for a Good Business Case - Chapter 20: Ten Things for Successful Project Assurance Part V: Appendices - Appendix A: Looking into PRINCE Qualifications - Appendix B: Glossary of the Main PRINCE2 Terms

    This work contains components of the model, which include staffing models and strategy, staffing support systems (legal compliance, planning, job analysis and rewards), core staffing systems (recruitment, selection, employment), and staffing system and retention management.

    When restructures, mergers, bankruptcies, and layoffs hit the workplace, employees and managers naturally find the resulting situational shifts to be challenging. But the psychological transitions that accompany them are even more stressful. Organizational transitions affect people; it is always people, rather than a company, who have to embrace a new situation and carry out the corresponding change. As veteran business consultant William Bridges explains, transition is successful when employees have a purpose, a plan, and a part to play. This indispensable guide is now updated to reflect the challenges of today's ever-changing, always-on, and globally connected workplaces. Directed at managers on all rungs of the corporate ladder, this expanded edition of the classic bestseller provides practical, step-by-step strategies for minimizing disruptions and navigating uncertain times.

    This book walks managers through every step of project oversight from start to finish. Thanks to the book's comprehensive information on everything from planning and budgeting to team building and after-project reviews, managers will master the discipline and skills they need to achieve stellar results without wasting time and money.

    Learn how to interpret questions and how to plan, structure and write your assignment or report. This free course, Essay and report writing skills, is designed to help you develop the skills you need to write effectively for academic purposes.

    The second addition to the Clients From Hell series taps freelance veterans for even more material. Interviews, resources, and particularly poignant tales of client insanity are all included alongside the fan-favourite anecdotes of freelancing dysfunction.For the first time, Clients From Hell takes a step back from finger-pointing and clever name-calling to inform the audience of how to make it as a creative professional. Step one: buy this book. Step two: take heed of these cautionary tales. Step three: we haven't thought of a step three yet. We'll worry about that when revisions come around.Anyone who has ever worked with clients may find these tales frighteningly familiar. New freelancers may think twice about their chosen profession - or at least find relief in the fact that they're not alone in absurd client interactions.And the rest of you? You can just laugh and enjoy your day job.

    Billions of interconnected devices will be monitoring the environment, transportation systems, factories, farms, forests, utilities, soil and weather conditions, oceans and resources Many of these sensors and actuators will be networked into autonomous sets, with much of the information being exchanged machine-to-machine directly and without human involvement. Machine-to-machine communications are typically terse. Most sensors and actuators will report or act upon small pieces of information - chirps. Burdening these devices with current network protocol stacks is inefficient, unnecessary and unduly increases their cost of ownership. This must change. The architecture of the Internet of Things will entail a widely distributed topology incorporating simpler chirp protocols towards at the edges of the network. Rethinking the Internet of Things describes reasons why we must rethink current approaches to the Internet of Things. Appropriate architectures that will coexist with existing networking protocols are described in detail. An architecture comprised of integrator functions, propagator nodes, and end devices, along with their interactions, is explored. What you'll learn Teaches the difference between the "normal" Internet and the Internet of Things, Describes a new architecture and its components in the "chirp" context. Explains the shortcomings of IP for IoT. Describes the anatomy of the IoT. Re-frames key ideas such as reliability. Describes how to build the IoT Who this book is forThought leaders, executives, architectural, standards and development leaders in the evolving IoT industry