The worst managers undermine inner work life, often unwittingly.As Teresa Amabile and Steven Kramer explain in The Progress Principle, seemingly mundane workday events can make or break employees’ inner work lives. But it’s forward momentum in meaningful work—progress—that creates the best inner work lives. Through rigorous analysis of nearly 12,000 diary entries provided by 238 employees in 7 companies, the authors explain how managers can foster progress and enhance inner work life every day.The book shows how to remove obstacles to progress, including meaningless tasks and toxic relationships. It also explains how to activate two forces that enable progress: (1) catalysts—events that directly facilitate project work, such as clear goals and autonomy—and (2) nourishers—interpersonal events that uplift workers, including encouragement and demonstrations of respect and collegiality.Brimming with honest examples from the companies studied, The Progress Principle equips aspiring and seasoned leaders alike with the insights they need to maximize their people’s performance.

    Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization's business strategy.Drawing on their own extensive experience, the authors cover the essential technical topics for designing, specifying, and validating a system. They also emphasize the importance of the business context in which large systems are designed. Their aim is to present software architecture in a real-world setting, reflecting both the opportunities and constraints that companies encounter. To that end, case studies that describe successful architectures illustrate key points of both technical and organizational discussions.Topics new to this edition include: Architecture design and analysis, including the Architecture Tradeoff Analysis Method (ATAM) Capturing quality requirements and achieving them through quality scenarios and tactics Using architecture reconstruction to recover undocumented architectures Documenting architectures using the Unified Modeling Language (UML) New case studies, including Web-based examples and a wireless Enterprise JavaBeans™ (EJB) system designed to support wearable computers The financial aspects of architectures, including use of the Cost Benefit Analysis Method (CBAM) to make decisions If you design, develop, or manage the building of large software systems (or plan to do so), or if you are interested in acquiring such systems for your corporation or government agency, use Software Architecture in Practice, Second Edition, to get up to speed on the current state of software architecture.

    

    But the principles and practices of software architecting–what the authors call the “science of hard decisions”–have been evolving for cloud, mobile, and other shifts. Now fully revised and updated, this book shares the knowledge and real-world perspectives that enable you to design for success–and deliver more successful solutions. In this fully updated Second Edition, you will: Learn how only a deep understanding of domain can lead to appropriate architecture Examine domain-driven design in both theory and implementation Shift your approach to code first, model later–including multilayer architecture Capture the benefits of prioritizing software maintainability See how readability, testability, and extensibility lead to code quality Take a user experience (UX) first approach, rather than designing for data Review patterns for organizing business logic Use event sourcing and CQRS together to model complex business domains more effectively Delve inside the persistence layer, including patterns and implementation.

    But when he took the helm in 2004, America was losing that war badly: despite vastly inferior resources and technology, Al Qaeda was outmaneuvering America’s most elite warriors. McChrystal came to realize that today’s faster, more interdependent world had overwhelmed the conventional, top-down hierarchy of the US military. Al Qaeda had seen the future: a decentralized network that could move quickly and strike ruthlessly. To defeat such an enemy, JSOC would have to discard a century of management wisdom, and pivot from a pursuit of mechanical efficiency to organic adaptability. Under McChrystal’s leadership, JSOC remade itself, in the midst of a grueling war, into something entirely new: a network that combined robust centralized communication with decentralized managerial authority. As a result, they beat back Al Qaeda. In this book, McChrystal shows not only how the military made that transition, but also how similar shifts are possible in all organizations, from large companies to startups to charities to governments. In a turbulent world, the best organizations think and act like a team of teams, embracing small groups that combine the freedom to experiment with a relentless drive to share what they’ve learned. Drawing on a wealth of evidence from his military career, the private sector, and sources as diverse as hospital emergency rooms and NASA’s space program, McChrystal frames the existential challenge facing today’s organizations, and presents a compelling, effective solution.

    If you are an organization that really needs to start grokking UX this book is also for you. " -- Chris Bernard, User Experience Evangelist, Microsoft User experience design is the discipline of creating a useful and usable Web site or application--one that's easily navigated and meets the needs of both the site owner and its users. But there's a lot more to successful UX design than knowing the latest Web technologies or design trends: It takes diplomacy, project management skills, and business savvy. That's where this book comes in. Authors Russ Unger and Carolyn Chandler show you how to integrate UX principles into your project from start to finish. - Understand the various roles in UX design, identify stakeholders, and enlist their support- Obtain consensus from your team on project objectives- Define the scope of your project and avoid mission creep- Conduct user research and document your findings- Understand and communicate user behavior with personas- Design and prototype your application or site- Make your product findable with search engine optimization- Plan for development, product rollout, and ongoing quality assurance

    It has led nothing short of a revolution in the entertainment industries, generating billions of dollars in annual revenue while capturing the imaginations of hundreds of millions of people in over 190 countries. But to reach these great heights, Netflix, which launched in 1998 as an online DVD rental service, has had to reinvent itself over and over again. This type of unprecedented flexibility would have been impossible without the counterintuitive and radical management principles that cofounder Reed Hastings established from the very beginning. Hastings rejected the conventional wisdom under which other companies operate and defied tradition to instead build a culture focused on freedom and responsibility, one that has allowed Netflix to adapt and innovate as the needs of its members and the world have simultaneously transformed.Hastings set new standards, valuing people over process, emphasizing innovation over efficiency, and giving employees context, not controls. At Netflix, there are no vacation or expense policies. At Netflix, adequate performance gets a generous severance, and hard work is irrel-evant. At Netflix, you don't try to please your boss, you give candid feedback instead. At Netflix, employees don't need approval, and the company pays top of market. When Hastings and his team first devised these unorthodox principles, the implications were unknown and untested. But in just a short period, their methods led to unparalleled speed and boldness, as Netflix quickly became one of the most loved brands in the world.Here for the first time, Hastings and Erin Meyer, bestselling author of The Culture Map and one of the world's most influential business thinkers, dive deep into the controversial ideologies at the heart of the Netflix psyche, which have generated results that are the envy of the business world. Drawing on hundreds of interviews with current and past Netflix employees from around the globe and never-before-told stories of trial and error from Hastings's own career, No Rules Rules is the fascinating and untold account of the philosophy behind one of the world's most innovative, imaginative, and successful companies.

    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.

    Strategic planning is essential. People's competencies should be measured and their weaknesses shored up. People crave feedback.These may sound like basic truths of our work lives today. But actually, they're lies. As strengths guru and bestselling author Marcus Buckingham and Cisco Leadership and Team Intelligence head Ashley Goodall show in this provocative, inspiring book, there are some big lies--distortions, faulty assumptions, wrong thinking--running through our organizational lives. Nine lies, to be exact. They cause dysfunction and frustration and ultimately result in a strange feeling of unreality that pervades our workplaces.But there are those who can get past the lies and discover what's real. These are freethinking leaders who recognize the power and beauty of our individual uniqueness, who know that emergent patterns are more valuable than received wisdom, and that evidence is more powerful than dogma. With engaging stories and incisive analysis, the authors reveal the essential truths that such freethinking leaders will recognize immediately: that it is the strength and cohesiveness of your team, not your company's culture, that matters most; that we need less focus on top-down planning and more on giving our people reliable, real-time intelligence; that rather than trying to align people's goals we should strive to align people's sense of purpose and meaning; that people don't want constant feedback, they want helpful attention. This is the real world of work.If you embrace each person's uniqueness and see this as key for all healthy organizations; if you reject dogma and engage with the real world; if you seek out emergent patterns and put your faith in evidence, not philosophy; if you thrill to the power of teams--if you do all of these, then you are a freethinking leader, and this book is for you.

    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.

    Caught between a traditional approach to program and portfolio management, and half-baked Agile methods at the team level, he struggles to help his company find a way out. Faced with a nearly impossible quest, he attends a conference desperately seeking a solution. There he finds a glimpse of hope—a method that applies the notion of Agility at a much higher scale. Inspired by this discovery, Ethan charges into action, launching the rollout of a new method at his company. But in no time, he runs into a brick wall which puts the rollout, and his own career, in grave danger. He comes to realize that the basic culture and his enterprise’s way of thinking are its biggest impediments to success. His quest leads him to understand that his own mindset is also part of the problem.... The reader will be pulled into the exciting action unfolding as Ethan leads his organization towards enterprise agility. Fictional, but based on a broad range of real-life implementations, this novel by Alex Yakyma provides a war chest of techniques and tools to support large-scale rollouts of Lean and Agile methods.

    Some can generate coherent user experiences, others produce confusing patchwork designs. Some inspire teams to contribute to them, while others are neglected. Some get better with time, more cohesive and better functioning; others get worse, becoming bloated and cumbersome.Throughout this book, Alla Kholmatova, previously a lead designer at FutureLearn, will share an approach and the key qualities of effective, enduring design systems. It’s based on Alla’s experiences, case-studies from AirBnB, Atlassian, Eurostar, TED, and Sipgate, plus 18 months of research and interviews — all attempting to figure out what works and what doesn’t work in real-life products. It may not answer every question, but it will help you figure out just the right strategy for establishing and evolving a design system in your organization.

    It was a breakthrough guide in how to drive high quality and customer value, while maintaining a singular focus on agile delivery principles. Fast forward to 2013 and much has changed.Scrum and the other agile methods are dominating the mainstream and new success stories seem to be forthcoming daily. However, there are still challenges and many surround the Product Owner role: scaling Scrum, sustaining quality, delivering and measuring value, providing team leadership, being a part of organizational transformation, and simple survival are all still in play. In other words, the role is still just plain HARD. The Second Edition of Scrum Product Ownership is being delivered to help with today’s challenges. It has more practical advice, real-world tactics, and more stories. It provides a framework of ideas to help today's Product Owners and their teams to better “Deliver the Goods”. However, it remains true to its heritage of guiding you towards becoming a GREAT Product Owner…from the Inside Out.

    That was before one pioneering work documented the underground computer revolution that was about to change our world forever. With groundbreaking profiles of Bill Gates, Steve Wozniak, MIT's Tech Model Railroad Club, and more, Steven Levy's Hackers brilliantly captured a seminal moment when the risk-takers and explorers were poised to conquer twentieth-century America's last great frontier. And in the Internet age, the hacker ethic-first espoused here-is alive and well.

    The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.