You'll also learn how to make your programs interactive and how to test your code safely before adding it to a project. In the second half of the book, you'll put your new knowledge into practice with three substantial projects: a Space Invaders-inspired arcade game, data visualizations with Python's super-handy libraries, and a simple web app you can deploy online.As you work through Python Crash Course, you'll learn how to: Use powerful Python libraries and tools, including matplotlib, NumPy, and PygalMake 2D games that respond to keypresses and mouse clicks, and that grow more difficult as the game progressesWork with data to generate interactive visualizationsCreate and customize simple web apps and deploy them safely onlineDeal with mistakes and errors so you can solve your own programming problemsIf you've been thinking seriously about digging into programming, Python Crash Course will get you up to speed and have you writing real programs fast. Why wait any longer? Start your engines and code!

    But honest and open conversations are not taking place between management and Agile delivery teams.In A Seat at the Table, CIO Mark Schwartz explores the role of IT leadership as it is now and opens the door to reveal IT leadership as it should be - an integral part of the value creation engine. With wit and easy style, Schwartz reveals that the only way to become an Agile IT leader is to be courageous - to throw off the attitude and assumptions that have kept CIOs from taking their rightful seat at the table. CIOs, step on up, your seat at the table is waiting for you.Listening Length: 9 hours and 20 minutes

    Both are about creation, creating ourselves, reimagining the future and, in a very real sense, building the world around us.’ – Jack Delosa, entrepreneur, investor and BRW Young Rich List Member Unwritten presents a startling, revisionist approach to our understanding of entrepreneurship and living a life that aligns with your purpose. Through personal reflection and stories of unconventional wisdom, adversity and success, Jack examines what it means to be great, how we can achieve our life’s best work, shape the world around us for good and leave a legacy far more valuable than wealth alone. Unwritten is a book that will inspire you to grow into your best self and make your life an example for those who want to do the same. Your future is unwritten. Reinvent tomorrow ‘Jack Delosa is a real entrepreneur. In Unwritten, he elegantly uncovers how to build something truly great.’ - Matt RockMan, co-founder of Seek, entrepreneur and investor ‘Jack Delosa is a heady mix of intelligence, passion, humour and humility. In Unwritten, he propels us to be better humans and in doing so de nes the new measure of success.’ - Megan Quinn, co-founder of NET-A-PORTER, non-executive director at UNICEF Australia

    The Unwritten Laws of Business is such a book. Originally published over 60 years ago as The Unwritten Laws of Engineering, it has sold over 100,000 copies, despite the fact that it has never been available before to general readers. Fully revised for business readers today, here are but a few of the gems you’ll find in this little-known business classic: If you take care of your present job well, the future will take care of itself.The individual who says nothing is usually credited with having nothing to say.Whenever you are performing someone else’s function, you are probably neglecting your own.Martyrdom only rarely makes heroes, and in the business world, such heroes and martyrs often find themselves unemployed.Refreshingly free of the latest business fads and jargon, this is a book that is wise and insightful, capturing and distilling the timeless truths and principles that underlie management and business the world over.The little book with the big history.In the summer of 2005, Business 2.0 published a cover story on Raytheon CEO William Swanson’s self-published pamphlet, Swanson’s Unwritten Rules of Management. Lauded by such chief executives as Jack Welch and Warren Buffett, the booklet becamea quiet phenomenon. As it turned out, much of Swanson’s book drew from a classic of business literature that has been in print for more than sixty years. Now, in a new edition revised and updated for business readers today, we are reissuing the 1944 classic that inspired a number of Swanson’s “rules”: The Unwritten Laws of Business. Filled with sage advice and written in a spare, engaging style, The Unwritten Laws of Business offers insights on working with others, reporting to a boss, organizing a project, running a meeting, advancing your career, and more. Here’s just a sprinkling of the old-fashioned, yet surprisingly relevant, wisdom you’ll find in these pages:If you have no intention of listening to, considering, and perhaps using, someone’s opinion, don’t ask for it.Count any meeting a failure that does not end up with a definite understanding as to what’s going to be done, who’s going to do it, and when.The common belief that everyone can do anything if they just try hard enough is a formula for inefficiency at best and for complete failure at worst.It is natural enough to “look out for Number One first,” but when you do, your associates will be noticeably disinclined to look out for you.Whether you’re a corporate neophyte or seasoned manager, this charming book reveals everything you need to know about the “unwritten” laws of business.

    Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.

    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

    Indeed, that's what computers are for. You can enlist your own computer to automate all of your project's repetitive tasks, ranging from individual builds and running unit tests through to full product release, customer deployment, and monitoring the system.Many teams try to do these tasks by hand. That's usually a really bad idea: people just aren't as good at repetitive tasks as machines. You run the risk of doing it differently the one time it matters, on one machine but not another, or doing it just plain wrong. But the computer can do these tasks for you the same way, time after time, without bothering you. You can transform these labor-intensive, boring and potentially risky chores into automatic, background processes that just work.In this eagerly anticipated book, you'll find a variety of popular, open-source tools to help automate your project. With this book, you will learn: How to make your build processes accurate, reliable, fast, and easy. How to build complex systems at the touch of a button. How to build, test, and release software automatically, with no human intervention. Technologies and tools available for automation: which to use and when. Tricks and tips from the masters (do you know how to have your cell phone tell you that your build just failed?) You'll find easy-to-implement recipes to automate your Java project, using the same popular style as the rest of our Jolt Productivity Award-winning Starter Kit books. Armed with plenty of examples and concrete, pragmatic advice, you'll find it's easy to get started and reap the benefits of modern software development. You can begin to enjoy pragmatic, automatic, unattended software production that's reliable and accurate every time.

    Deep inside, we sense that more is possible. We long for soulful workplaces, for authenticity, community, passion, and purpose.In this groundbreaking book, the author shows that every time, in the past, when humanity has shifted to a new stage of consciousness, it has achieved extraordinary breakthroughs in collaboration. A new shift in consciousness is currently underway. Could it help us invent a more soulful and purposeful way to run our businesses and nonprofits, schools and hospitals?A few pioneers have already cracked the code and they show us, in practical detail, how it can be done. Leaders, founders, coaches, and consultants will find this work a joyful handbook, full of insights, examples, and inspiring stories.ADVANCE PRAISE"Congratulations on a spectacular treatise! This is truly pioneering work. In terms of integral sophistication, there is simply nothing like it out there."--Ken Wilber, from the Foreword"The most exciting book I've read in years on organization design and leadership models."--Jenny Wade, Ph.D., Author of Changes of Mind"A book like Reinventing Organizations only comes along once in a decade. Sweeping and brilliant in scope, it is the Good To Great for a more enlightened age. What it reveals about the organizational model of the future is exhilarating and deeply hopeful."--Norman Wolfe, Author of The Living Organization"A comprehensive, highly practical account of the emergent worldview in business. Everything you need to know about building a new paradigm organization!"--Richard Barrett, Chairman and Founder, Barrett Values Center"Frederic Laloux has done business people and professionals everywhere a signal service. He has discovered a better future for organizations by describing, in useful detail, the unusual best practices of today."--Bill Torbert, Author of Action Inquiry"As the rate of change escalates exponentially, the old ways of organizing and educating, which were designed for efficiency and repetition, are dying. Frederic Laloux is one of the few management leaders exploring what comes next. It's deeply different."--Bill Drayton, Founder, Ashoka: Innovators for the Public

    This radically simple concept is the heart of Leaders Open Doors.This book presents a fresh and unique take on leadership that will benefit experienced leaders and those just starting their leadership journeys. With a little courage, anyone at any level can be a leader.Drawing on two decades of experience, author and speaker, Bill Treasurer, in this new second edition, combines personal stories and anecdotes to illustrate how (and how not) to inspire people. He approaches these ideas with the belief that great leadership is not hierarchical--it is the peoples' willingness to take initiative and reach their goals that is crucial to successful leadership.

    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

    This behavior is so ingrained, so subtle, and so often mistaken for true intelligence that identifying it, calling it out, or compiling it into an exhaustive digest has never been attempted. Until now.Complete with illustrated tips, examples, and scenarios, 100 Tricks gives you actionable ways to use words like 'actionable', in order to sound smart. Every type of meeting is covered, from general meetings where you stopped paying attention almost immediately, to one-on-one meetings you zoned out on, to impromptu meetings you were painfully subjected to at the last minute. It’s all here.Open this book to any page and find an easy-to-digest trick with an even easier-to-digest illustration, guiding you on: how to nail the big meeting by pacing and nodding, the most effective ways to listen to your coworkers while still completely ignoring them, and the key to making your presentations 'interactive'.If you hadn’t noticed these behaviors before, you will see them now - from your colleagues, your managers, and soon yourself. Each trick is a mirror to the reality of what happens in meetings, told in the form of hilariously bad advice - advice that you might just want to take. But probably not. But maybe.

    This is the 12th edition of 'Marketing Management' which preserves the strengths of previous editions while introducing new material and structure to further enhance learning.

    Information is provided on the fundamental concepts of table and graph design, the numbers and knowledge most suitable for display in a graphic form, the best tabular means to communicate certain ideas, and the component-level aspects of design. Analysts, technicians, and managers will appreciate the solid theory behind this outline for ensuring that tables and graphs present quantitative business information in a truthful, attractive format that facilitates better decision making.

    Rather than pursuing development speed at any price, the authors emphasize subjecting time-to-market decisions to the same hard-nosed business logic used for other management decisions. "Developing Products" is unique in providing tools for trading off schedule against other business objectives. It integrates powerful methods to manage risk and use resources effectively with proven techniques to accelerate product development.

    Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.