A key component of the facilitator-lead Five Dysfunctions of a Team Workshop, the Team Assessment delivers what the name implies "a team assessment" rather than an individual self-assessment. It provides participants with an opportunity to begin exploring the pitfalls that are side-tracking their team. Easy to use, the Assessment is ideal for team off-sites, retreats, or a series of team development meetings. It will help teams of all types increase their cohesiveness and productivity.

    But, although they use these patterns purposefully, they often use them informally and nearly unconsciously. This book organizes this substantial emerging "folklore" of system design -- with its rich language of system description -- and closes the gap between the useful abstractions (constructs and patterns) of system design and the current models, notations and tools. It identifies useful patterns clearly, gives examples, compares them, and evaluates their utility in various settings -- allowing readers to develop a repertoire of useful techniques that goes beyond the single-minded current fads. KEY TOPICS: Examines the ways in which architectural issues can impact software design; shows how to design new systems in principled ways using well-understood architectural paradigms; emphasizes informal descriptions, touching lightly on formal notations and specifications, and the tools that support them; explains how to understand and evaluate the design of existing software systems from an architectural perspective; and presents concrete examples of actual system architectures that can serve as models for new designs. MARKET: For professional software developers looking for new ideas about system organization.

    

    The coverage also features learning aids.

    As they helped grow Google from a young start-up to a global icon, they relearned everything they knew about management. How Google Works is the sum of those experiences distilled into a fun, easy-to-read primer on corporate culture, strategy, talent, decision-making, communication, innovation, and dealing with disruption.The authors explain how the confluence of three seismic changes - the internet, mobile, and cloud computing - has shifted the balance of power from companies to consumers. The companies that will thrive in this ever-changing landscape will be the ones that create superior products and attract a new breed of multifaceted employees whom the authors dub 'smart creatives'. The management maxims ('Consensus requires dissension', 'Exile knaves but fight for divas', 'Think 10X, not 10%') are illustrated with previously unreported anecdotes from Google's corporate history.'Back in 2010, Eric and I created an internal class for Google managers,' says Rosenberg. 'The class slides all read 'Google confidential' until an employee suggested we uphold the spirit of openness and share them with the world. This book codifies the recipe for our secret sauce: how Google innovates and how it empowers employees to succeed.'

    SAFe addresses this primary goal, and offers these further benefits: reduced time-to-market, improved quality, stronger alignment across geographically distributed multi-disciplinary teams, and collaboration across teams to deliver meaningful value to customers with reduced cycle time." --Sundaresan Jagadeesan, SW CoE Program Director, Philips To succeed in today's adapt-or-die marketplace, businesses must be able to rapidly change the way they create and deliver value to their customers. Hundreds of the world's most successful companies-including Intel, Capital One, AstraZeneca, Cisco, and Philips-have turned to the Scaled Agile Framework(R) (SAFe(R)) to achieve agility at scale and maintain a competitive edge. SAFe(R) 4.5 Distilled: Applying the Scaled Agile Framework(R) for Lean Enterprises explains how adopting SAFe can quickly improve time to market and increase productivity, quality, and employee engagement. In this book, you will Understand the business case for SAFe: its benefits, the problems it solves, and how to apply it Get an overview of SAFe across all parts of the business: team, program, value stream, and portfolio Learn why SAFe works: the power of SAFe's Lean-Agile mindset, values, and principles Discover how systems thinking, Agile development, and Lean product development form the underlying basis for SAFe Learn how to become a Lean-Agile leader and effectively drive an enterprise-wide transformation Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

    Have you ever opened a Kindle book to find that the font started out way too small or way too large? Have you tried to change to a different font while reading and discovered you couldn't? Have you jumped to a new chapter in a Kindle book and seen that the chapter heading lost its formatting? Has a Kindle completely ignored formatting you knew was in the book? According to Amazon, the simplest way to publish your Kindle book is to upload an HTML file you've saved from Microsoft Word or another app. By itself, that method can bring you maybe 80% of the way to a well-formatted, trouble-free ebook. But what about the other 20%? In this follow-up to his bestselling -From Word to Kindle, - Aaron Shepard takes your saved HTML as a starting point and tells how to quickly tweak and tune it to avoid common problems. Assuming no knowledge of HTML, he introduces the basics of the language, then reveals how to use find-and-replace and macros to touch up an entire book in seconds! If you're serious about Kindle publishing and you're technically inclined -- but not a full-fledged geek -- Aaron provides the tips you need to bring your Kindle book to the next level, making it something truly to be proud of. ///////////////////////////////////////////////// Aaron Shepard is a foremost proponent of the new business of profitable self publishing, which he has practiced and helped develop since 1998. He is the author of -Aiming at Amazon, - -POD for Profit, - -Perfect Pages, - and Amazon's #1 and #2 bestselling paid books on Kindle formatting, -From Word to Kindle- and -Pictures on Kindle.- ///////////////////////////////////////////////// CONTENTS Getting Started 1 WORKING WITH HTML HTML and Kindle HTML Export HTML Editing HTML Processing HTML Basics HTML Checking HTML Cleanup HTML Testing 2 HTML FIXES Fixes for Fonts Fixes for Paragraphs Fixes for Headings Fixes for Line Breaking Fixes for Pictures Fixes for Navigation ///////////////////////////////////////////////// SAMPLE Here are some of the things you can accomplish through changes in HTML. * Adjust bookmarks so headings retain proper formatting when jumped to. * Remove settings that stop the user from choosing their own. * Keep fonts from appearing much too small or much too large when the book is opened. * Make sure indents and other spacing stays relative to larger and smaller font sizes. * Avoid line breaks that leave short words dangling at the ends of lines or paragraphs. * Make up for features lost in translation from your word processor, like nonbreaking hyphens. * Stop -ghost hyphens- from appearing in the middle of words. * Keep pages of text from disappearing for some users. * Prevent the Kindle from applying its own defaults in place of your settings.

    Now, they build on their message with a bold, iconoclastic strategy for creating the ideal company culture—what they call "the calm company." Their approach directly attack the chaos, anxiety, and stress that plagues millions of workplaces and hampers billions of workers every day.Long hours, an excessive workload, and a lack of sleep have become a badge of honor for modern professionals. But it should be a mark of stupidity, the authors argue. Sadly, this isn’t just a problem for large organizations—individuals, contractors, and solopreneurs are burning themselves out the same way. The answer to better productivity isn’t more hours—it’s less waste and fewer things that induce distraction and persistent stress.It’s time to stop celebrating Crazy, and start celebrating Calm, Fried and Hansson assert.Fried and Hansson have the proof to back up their argument. "Calm" has been the cornerstone of their company’s culture since Basecamp began twenty years ago. Destined to become the management guide for the next generation, It Doesn't Have to Be Crazy at Work is a practical and inspiring distillation of their insights and experiences. It isn’t a book telling you what to do. It’s a book showing you what they’ve done—and how any manager or executive no matter the industry or size of the company, can do it too.

    More than three years in development and subjected to numerous industry reviews, the 85 patterns in this full-color book provide the most successful and proven design techniques to overcoming the most common and critical problems to achieving modern-day SOA. Through numerous examples, individually documented pattern profiles, and over 400 color illustrations, this book provides in-depth coverage of:• Patterns for the design, implementation, and governance of service inventories–collections of services representing individual service portfolios that can be independently modeled, designed, and evolved.• Patterns specific to service-level architecture which pertain to a wide range of design areas, including contract design, security, legacy encapsulation, reliability, scalability, and a variety of implementation and governance issues.• Service composition patterns that address the many aspects associated with combining services into aggregate distributed solutions, including topics such as runtime messaging and message design, inter-service security controls, and transformation.• Compound patterns (such as Enterprise Service Bus and Orchestration) and recommended pattern application sequences that establish foundational processes. The book begins by establishing SOA types that are referenced throughout the patterns and then form the basis of a final chapter that discusses the architectural impact of service-oriented computing in general. These chapters bookend the pattern catalog to provide a clear link between SOA design patterns, the strategic goals of service-oriented computing, different SOA types, and the service-orientation design paradigm.This book series is further supported by a series of resources sites, including soabooks.com, soaspecs.com, soapatterns.org, soamag.com, and soaposters.com.

    - Build an Angular 2 application from scratch using TypeScript and the Angular command line interface. - Write code using the paradigm of reactive programming with RxJS and Observables. - Know how to Unit Test Angular 2 using Jasmine, Karma and the Angular Test Bed The first chapter in the course is a quickstart where you dive straight into writing your first Angular 2 application. We use the web editor plunker so you can get stuck in writing code ASAP. In this quickstart you'll get a 50,000 foot view of the major features of Angular 2. Then chapter by chapter we go much deeper into each of these features. I'll cover the theory for that feature, using plunker as much as possible so you can try out the code yourself in a browser. Then you'll practice what you've learnt with either an online quiz or a set of flash cards. You are going to learn all about:- - Typescript & ES6 Javascript. - Components & Binding - Directives - Dependancy Injection & Services - Angular Modules & Bootstrapping your Angular application. - SPAs & Routing - Angular CLI - Forms - Reactive Programming with RXJs - HTTP - Unit Testing The ideal student is an existing web developer, with some JavaScript knowledge that wants to add Angular 2 to their skill set. Or perhaps you are an existing Angular 1 developer who wants to level up to Angular 2. You do need to be comfortable with at least the ES5 version of JavaScript. We'll be using a UI framework called twitter bootstrap throughout the course but you still must know HTML and some CSS.

    This book demystifies agile methodologies: why they’re designed the way they are, what problems they address, and the values, principles, and ideas they embody.Learning Agile helps you recognize the principles that apply to development problems specific to your team, company, and projects. You’ll discover how to use that information to guide your choice of methodologies and practices.With this book you’ll learn:Values that effective software teams possessThe methodologies that embody those valuesThe practices that make up those methodologiesAnd principles that help you bring those values, methodologies, and practices to your team and your company

    With 97 short and extremely useful tips for engineering managers, you'll discover new approaches to old problems, pick up road-tested best practices, and hone your management skills through sound advice.Managing people is hard, and the industry as a whole is bad at it. Many managers lack the experience, training, tools, texts, and frameworks to do it well. From mentoring interns to working in senior management, this book will take you through the stages of management and provide actionable advice on how to approach the obstacles you'll encounter as a technical manager.A few of the 97 things you should know:"Three Ways to Be the Manager Your Report Needs" by Duretti Hirpa"The First Two Questions to Ask When Your Team Is Struggling" by Cate Huston"Fire Them!" by Mike Fisher"The 5 Whys of Organizational Design" by Kellan Elliott-McCrea"Career Conversations" by Raquel V�lez"Using 6-Page Documents to Close Decisions" by Ian Nowland"Ground Rules in Meetings" by Lara Hogan

    It runs on PCs rather than servers and is ideal for small- to mid-sized businesses and households. But Access is still intimidating to learn. It doesn't help that each new version crammed in yet another set of features; so many, in fact, that even the pros don't know where to find them all. Access 2007 breaks this pattern with some of the most dramatic changes users have seen since Office 95. Most obvious is the thoroughly redesigned user interface, with its tabbed toolbar (or "Ribbon") that makes features easy to locate and use. The features list also includes several long-awaited changes. One thing that hasn't improved is Microsoft's documentation. To learn the ins and outs of all the features in Access 2007, Microsoft merely offers online help.Access 2007: The Missing Manual was written from the ground up for this redesigned application. You will learn how to design complete databases, maintain them, search for valuable nuggets of information, and build attractive forms for quick-and-easy data entry. You'll even delve into the black art of Access programming (including macros and Visual Basic), and pick up valuable tricks and techniques to automate common tasks -- even if you've never touched a line of code before. You will also learn all about the new prebuilt databases you can customize to fit your needs, and how the new complex data feature will simplify your life. With plenty of downloadable examples, this objective and witty book will turn an Access neophyte into a true master.

    The RESTful approach to web services design is rapidly become the approach of choice. Unfortunately, too few people have truly solid REST API design skills, and discussions of REST can become bogged down in dry theory.The REST API Design Handbook is a simple, practical guide to aid software engineers and software architects create lasting, scalable APIs based on REST architectural principles. The book provides a sound foundation in discussing the constraints that define a REST API. It quickly goes beyond that into the practical aspects of implementing such an API in the real world.Written by cloud computing expert George Reese, The REST API Design Handbook reflects hands on work in consuming many different third party APIs as well the development of REST-based web services APIs. It addresses all of the debates the commonly arise while creating these APIs. Subjects covered include:* REST architectural constraints* Using HTTP methods and response codes in an API* Authenticating RESTful API calls* Versioning* Asynchronous Operations* Pagination and Streaming* Polling and Push Notifications* Rate Limiting

    A focus is placed on the principles and practices of decomposing a complex problem space as well as the implementation patterns and best practices for shaping a maintainable solution space.