This book talks about how one can acquire the expertise to forge leaders, I have delved deep into my interactions with inspiring leaders/mentors who have carved a niche for themselves & benchmarked their best practices for you to imbibe.There is a lot of Vedic & Greco-Roman cultural influence which you shall find in this book, as it draws a parallel between ancient knowledge & its modern interpretation.Each of the 22 Chapters should be perceived as a tool & this book aspires to serve as a instrument to learn techniques to develop leaders & forge them into champions.

    Written by Mike Griffiths, PMI Agile Certified Practitioner and original member of the PMI-ACP® Steering Committee, PMI-ACP® Exam Prep, Premier Edition is specifically written for people who plan to sit for the PMI-ACP® examination.Features of this worldwide best-selling resource include the following:- Practice exam questions—over 100 throughout the book.- Dozens of visuals and graphics for concept explanation.- Identification of ‘exam significance’ for each Agile topic.- A focus on real-world Agile project issues.- Exclusive exercises and Tricks of the Trade®.

    You'll find complete coverage of all exam objectives, including key topics such as project planning, execution, delivery, closure, and others. CompTIA's Project+ is the foundation-level professional exam in the complex world of project management; certified project managers often choose to go on and obtain their Project Management Professional (PMP) certifications as well Provides complete coverage of all exam objectives for CompTIA's first update to the Project+ exam in six years Covers project planning, execution, delivery, change, control, communication, and closure Demonstrates and reinforces exam preparation with practical examples and real-word scenarios Includes a CD with Sybex test engine, practice exams, electronic flashcards, and a PDF of the book Approach the new Project+ exam with confidence with this in-depth study guide! Reviews

    Focused on spurring next-generation growth, guiding mergers and acquisitions, and embracing disruption and innovation, ZONE TO WIN is a high-powered tool for driving your company above and beyond its limitations, its definitions of success, and ultimately, its competitors. Moore’s classic bestseller, CROSSING THE CHASM, has sold more than one million copies by addressing the challenges faced by start-up companies. Now ZONE TO WIN is set to guide established enterprises through the same journey. “For any company, regardless of size or industry, ZONE TO WIN is the playbook for succeeding in today’s disruptive, connected, fast-paced business world.” —Marc Benioff, CEO, Salesforce “Once again Geoffrey Moore weighs in with a prescient examination of what it takes to win in today’s competitive, disruptive business environment.” —Satya Nadella, CEO, Microsoft "With this book, Geoffrey Moore continues to lead us all through ever-changing times...His work has changed the game of changing the game!" —Gary Kovacs, CEO, AVG “ZONE TO WIN uses crystal-clear language to describe the management plays necessary to win in an ever-disrupting marketplace. Regardless of your level of management experience, you will find this book an invaluable tool for building long-term success for your business.” —Lip-Bu Tan, President and CEO, Cadence Design Systems

    Rose Randall is the archetypical reluctant project manager. Following a painful project failure years ago, Rose s life is cast into chaos when she is once again thrown into the role against her wishes. Faced with a struggling project, help comes from an unexpected source guiding Rose in the direction of Real Options.When you have read Commitment , you:* understand what the Real Options model is;* can apply the Real Options model to manage project risks successfully;* understand why much of your life involves options that you currently are treating as commitments;* see the world through a different filter opening up many new possibilities;* understand the difference between Commitments and Options.Because the book will:* provide specific examples of how a project can manage its risks using the Real Options model;* outline a simple technique for making decisions;* make you aware of all the decisions you make every day;* build your confidence in your ability to decide when to commit and when to leave options open.In short, this book is indispensable for new and experienced project managers plus anyone else who is interested in knowing more about managing large projects.

    It’s helpful for learning Agile and Scrum, and also for a basic preparation for the PSM I exam (Professional Scrum Master level 1). It can also act as a simple reference for Scrum practitioners.

    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.

    In today's agile environments, these "soft" skills have grown even more crucial to success as an architect. For many developers, however, these skills don't come naturally-and they're rarely addressed in formal training. Now, long-time software architect Dave Hendricksen helps you fill this gap, supercharge your organizational impact, and quickly move to the next level in your career. In 12 Essential Skills for Software Architects, Hendricksen begins by pinpointing the specific relationship, personal, and business skills that successful architects rely upon. Next, he presents proven methods for systematically developing and sharpening every one of these skills, from negotiation and leadership to pragmatism and vision. From start to finish, this book's practical insights can help you get the architect position you want-and thrive once you have it! The soft skills you need... ...and a coherent framework and practical methodology for mastering them! Relationship skills Leadership, politics, gracious behavior, communication, negotiation Personal skills Context switching, transparency, passion Business skills Pragmatism, vision, business knowledge, innovation

    The generation that was raised in an age of instant communication, questioning authority and traditions, and Ritalin has begun tearing down the corporate ladder, communicating on the fly, and bringing play to work. But even with all the exciting potential that lies ahead for these creative, bold thinkers, it will all be for not if they cannot effectively bridge the gap between the hierarchical management style of senior executives and the casual, more collaborative approach of their peers.In Manager 3.0, the first-ever management guide written exclusively for the Millennial generation, readers will learn how to master crucial skills such as dealing with difficult people, delivering constructive feedback, and making tough decisions--while gaining insight into the four generations--yes, four!--currently in the workplace and how they can successfully bring out the best in each.Packed with interviews and examples from companies like Zappos, Groupon, Southwest Airlines, and Google, this invaluable, one-of-a-kind resource will help these promising new managers connect with and encourage the unique talents of the generations around them, while also developing an effective leadership style of their own.

    The Scrum Guide documents the Scrum framework and is maintained by Scrum’s creators, Ken Schwaber and Jeff Sutherland.

    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

    This work covers the project lifecycle, addressing every key issue participants face: politics, people, process, project management, and tools.

    The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?"Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.Readers will come away from this book understanding- How to get testers engaged in agile development- Where testers and QA managers fit on an agile team- What to look for when hiring an agile tester- How to transition from a traditional cycle to agile development- How to complete testing activities in short iterations- How to use tests to successfully guide development- How to overcome barriers to test automationThis book is a must for agile testers, agile teams, their managers, and their customers.

    

    And you can, too. Come take this amazing journey with Armando Montelongo.