Detailing the technical indicators and money management strategies that have worked best for him, T. Livingston breaks down what every savvy trader needs to profit in today’s stock market. Topics discussed include how to analyze the general market, which stocks to trade, when to buy, position sizing, profit targets, and selling rules. Swing Into It provides a variety of different examples so that the reader will be prepared for various market scenarios. Detailed sample trades are included so that the reader can see how Livingston thinks throughout each phase of his trades. If you’re looking to get started in swing trading or seeking to refine your trading system, Swing Into It belongs in your library.

    In its most simple form, earned value equates to fundamental project management. This is not a new book, but rather it is an updated book. Authors Quentin Fleming and Joel Koppelman have made some important additions. In many cases, there will be no changes to a given section. But in other sections, the authors have made substantial revisions to what they had described in the first edition. Fleming and Koppelman’s goal remains the same with this update: describe earned value project management in its most fundamental form, for application to all projects, of any size or complexity. Writing in an easy-to-read, friendly, and humorous style characteristic of the best teachers, Fleming and Koppelman have identified the minimum requirements that they feel are necessary to use earned value as a simple tool for project managers. They have also witnessed the use of simple earned value on software projects, and find it particularly exciting. Realistically, a Cost Performance Index (CPI) is the same whether the project is a multibillion-dollar high-technology project, or a simple one hundred thousand-dollar software project. A CPI is a CPI … period. It is a solid metric that reflects the health of the project. In every chapter, Fleming and Koppelman stick with using simple stories to define their central concept. Their project examples range from peeling potatoes to building a house. Examples are in round numbers, and most formulas get no more complicated than one number divided by another. Earned Value Project Management—Second Edition may be the best-written, most easily understood project management book on the market today. Project managers will welcome this fresh translation of jargon into ordinary English. The authors have mastered a unique "early-warning" signal of impending cost problems in time for the project manager to react.

    Our increasingly complex world demands that we continuously learn from failures (and successes) in order to survive and thrive. And yet, our learning is too often undermined. We construct biased but comfortable stories, which often feature a simple, single "root cause"--a villain, someone to take the blame. Having done that, we short-circuit the possibility of developing any deeper understanding of the complex systems we work with. With this common approach, our systems will become more fragile and drift into failure. In this concise and entertaining book, I.T. veteran Dave Zwieback describes an incident that threatens the very existence of a large financial institution, and the counterintuitive steps its leadership took to stop the downward spiral. Their novel approach is grounded in proven concepts from complexity science, resilience engineering, human factors, cognitive science, and organizational psychology. It allows us to identify the underlying conditions for failure, and make our systems (and organizations) safer and more resilient.- Get a clear understanding of the downside of blame- Learn how to identify (and counteract) cognitive biases in groups- See how organizations can determine the real root cause of problems- Establish real accountability with your organization- Use the Learning Review Framework to fully learn from failures of complex systems- Find practical insights and tips for moving beyond blame in your own organization

    Edited by the Sustainability Institute’s Diana Wright, this essential primer brings systems thinking out of the realm of computers and equations and into the tangible world, showing readers how to develop the systems-thinking skills that thought leaders across the globe consider critical for 21st-century life.Some of the biggest problems facing the world—war, hunger, poverty, and environmental degradation—are essentially system failures. They cannot be solved by fixing one piece in isolation from the others, because even seemingly minor details have enormous power to undermine the best efforts of too-narrow thinking.While readers will learn the conceptual tools and methods of systems thinking, the heart of the book is grander than methodology. Donella Meadows was known as much for nurturing positive outcomes as she was for delving into the science behind global dilemmas. She reminds readers to pay attention to what is important, not just what is quantifiable, to stay humble, and to stay a learner.In a world growing ever more complicated, crowded, and interdependent, Thinking in Systems helps readers avoid confusion and helplessness, the first step toward finding proactive and effective solutions.

    These innovative private sector partnerships answer perhaps the most pressing issue facing business and thought leaders today: how to practice capitalism in a way that satisfies the need for both profit and a healthy, sustainable planet. Mainwaring provides case studies from companies such as P&G, Walmart, Starbucks, Pepsi, Coca-Cola, Toyota, Nike, Whole Foods, Patagonia, and Nestle as well as a bold plan for how corporations need to rethink their strategies."

    This is a must-have marketing reference.

    All I Need to Know About Manufacturing I Learned in Joe's Garage: World Class Manufacturing Made Simple

    It:Incorporates the "Business Model Canvas" as the organizing principle for startup hypothesesProvides separate paths and advice for web/mobile products versus physical productsOffers a wealth of detailed instruction on how to get, keep, and grow customers recognizing the different techniques for web and physical channelsAnd teaches a "new math" for startups: "metrics that matter for fueling growth"The Startup Owner's Manual is a step-by-step, near-encyclopedic reference manual or "how to" for building a successful, scalable startup. Want to know what to do the first, week, month or year?What's the right distribution channel for your product?How to get traffic to your web site? …and how to activate customers or users on arrival?Who are the right "first customers," and why? …plus many more great tips in nearly 500 pages, complete with index, glossary, and Customer Development ChecklistsIt's the indispensible reference guide for any startup founder, entrepreneur, investor or educator.

    It describes the Disciplined Agile Delivery (DAD) process decision framework and then works through a case study describing a typical agile team’s experiences adopting a disciplined agile approach. The book describes how the team develops the first release of a mission-critical application while working in a legacy enterprise environment. It describes their experiences from beginning-to-end, starting with their initial team initiation efforts through construction and finally to deploying the solution into production. It also describes how the team stays together for future releases, overviewing their process improvement efforts from their Scrum-based beginnings through to a lean continuous delivery approach that fits in with their organization’s evolving DevOps strategy. The DAD framework is a hybrid of existing methods such as Scrum, Kanban, Agile Modeling, SAFe, Extreme Programming, Agile Data, Unified Process and many others. DAD provides the flexibility to use various approaches and plugs the gaps not addressed by mainstream agile methods. In a nutshell, DAD is “pragmatic agile.” DAD describes proven strategies to adapt and scale your agile initiatives to suit the unique realities of your enterprise without having to figure it all out by yourself. Here’s an overview of what each chapter covers: * Chapter 1: Introduction. This chapter provides a quick overview of the book and a brief history of Disciplined Agile. * Chapter 2: Reality over Rhetoric. This chapter explores several common myths about DAD and more importantly disproves them. * Chapter 3: Disciplined Agile Delivery in a Nutshell. This chapter provides a brief yet comprehensive overview of the DAD framework. * Chapter 4: Introduction to the Case Study. This chapter introduces us to the team, describes the market opportunity that they hope to address, and describes the environment in which they’re working. * Chapter 5: Inception. The team’s initiation effort includes initial requirements modeling and planning with their stakeholders in a streamlined manner, initial architecture modeling, setting up their physical work environment, setting up the start of their tooling infrastructure, initial risk identification, and finally securing stakeholder support and funding for the rest of the first release. * Chapters 6 through 10: Construction. These chapters each describe a single Construction iteration, sharing the team’s experiences during each of those two-week timeboxes. * Chapter 11: Transition. The two-week transition phase focuses on final testing and fixing, training the support/help-desk staff, finishing a few short end-user “how to” videos, and deploying the solution into production. * Chapter 12: Future Releases. This chapter overviews the team’s improvement efforts over the next few releases, describing how they evolve from the agile Scrum-based lifecycle to a leaner approach and eventually to continuous delivery. * Chapter 13: Closing Thoughts. This chapter overviews the disciplined agile resources that are available to you. * Appendix: The Disciplined Agile IT Department. This short appendix overviews our ongoing work on the Disciplined Agile framework to address the full scope of an IT department. At 102 pages, you should find this book to be a quick, informative read.

    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.

    If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book."-- Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L. "The first edition of this book told us what XP was--it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the 'why' of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the 'what' and the 'why, ' we can now all set out to confidently work on the 'how' how to run our projects better, and how to get agile techniques adopted in our organizations."-- Dave Thomas, The Pragmatic Programmers LLC "This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there's an excellent chapter on 'primary practices, ' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change.' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk."-- Ed Yourdon, author and consultant "XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline."-- Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software " Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled 'extreme.'..."-- Lou Mazzucchelli, Fellow, Cutter Business Technology Council "If your organization is ready for a change in the way it develops software, there's the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years."-- Philippe Kruchten, UBC, Vancouver, British Columbia "Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity."-- Mary Poppendieck, author of Lean Software Development: An Agile Toolkit "Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both

    With this practical book, you'll explore the often-misunderstood practice of user story mapping, and learn how it can help keep your team stay focused on users and their experience throughout the development process.You and your team will learn that user stories aren't a way to write better specifications, but a way to organize and have better conversations. This book will help you understand what kinds of conversations you should be having, when to have them, and what to keep track of when you do. Learn the key concepts used to create a great story map. Understand how user stories really work, and how to make good use of them in agile and lean projects. Examine the nuts and bolts of managing stories through the development cycle. Use strategies that help you continue to learn before and after the product's release to customers and usersUser Story Mapping is ideal for agile and lean software development team members, product managers and UX practitioners in commercial product companies, and business analysts and project managers in IT organizations—whether you're new to this approach or want to understand more about it.

    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.

    Here's how to handle them.If you read nothing else on managing people, read these 10 articles (featuring “Leadership That Gets Results,” by Daniel Goleman). We've combed through hundreds of Harvard Business Review articles and selected the most important ones to help you maximize your employees' performance.HBR's 10 Must Reads on Managing People will inspire you to:• Tailor your management styles to fit your people• Motivate with more responsibility, not more money• Support first-time managers• Build trust by soliciting input• Teach smart people how to learn from failure• Build high-performing teams• Manage your bossThis collection of best-selling articles includes: featured article "Leadership That Gets Results" by Daniel Goleman, "One More Time: How Do You Motivate Employees?" "The Set-Up-to-Fail Syndrome," "Saving Your Rookie Managers from Themselves," "What Great Managers Do," "Fair Process: Managing in the Knowledge Economy," "Teaching Smart People How to Learn," "How (Un)ethical Are You?" "The Discipline of Teams," and "Managing Your Boss."

    Moms in particular will welcome this trend.  A full 60% wish they had a flexible work option. But companies see advantages too in the way remote work increases their talent pool, reduces turnover, lessens their real estate footprint, and improves the ability to conduct business across multiple time zones, to name just a few advantages.  In Remote, inconoclastic authors Fried and Hansson will convince readers that letting all or part of work teams function remotely is a great idea--and they're going to show precisely how a remote work setup can be accomplished.