Authentic knowledge body of Scrum is Scrum Guide. It is too dense to absorb without context and correlations. This book reveals Scrum as defined in 'The Scrum Guide 2016' with context and correlations using Active Learning technique. It is all-in-one guide for Professional Scrum Master (PSM 1) aspirants, with comprehensive Scrum material, tips, and 250+ practice questions.

    You may not like Facebook, but you can't deny its success. And to a large degree, that success stems from the "move fast" ethos. The entire culture of Facebook is built for speed.Move Fast is an exploration of modern software strategies and tactics through the lens of Facebook. Relying on in-depth interviews with more than two dozen Facebook engineers, this book explores the product strategy, cultural principles, and technologies that made Facebook the dominant social networking company. Most importantly, Move Fast investigates how you can apply those strategies to your creative projects.It's not easy to build a software company, but once you know how to move fast, your company will be prepared to build a strategy that benefits from the world's rapid changes, rather than suffering from them.

    Chanakya who was born around 3rd BC in Bharat (now Hindustan), astute, shrewd and ruthless political master. Equally selfless and patriotic teacher who politically united the small states post invasion of Greeks and reclaimed the boundaries of Bharat stretching from Puruvarsha (Persia, now Iran), Gansthan (now Afghanistan) to far east of Magadh (Bihar state). We know Chanakya for his Niti-shashtras, for his voluminous work on economy, maxims of wisdom and intelligence. But we do not know much about minute details with which he governed the country at that time. We do not know, during his time of around 3rd BCE, at how much advance stage the economy, public life, administration, industries, defence mechanisms, taxations, public-private partnerships, foreign policy, judicial systems, banking and accounting systems ….. were there in India. It seems, they all were in more than perfect stage compared to present scenario factoring advancement in science and technology etc. We will look at each of them one by one. In this book, “Chanakya Niti on Corruption”, we will take a look at corruption. What Chanakya thinks about sources of corruption, ways of finding about corruption, judgements and punishments of corruptions etc. Chanakya knows very well that just like it is impossible to know when and how much water a fish drinks, it is utmost difficult to know how much money government officials steal away while in charge of it. Knowing human nature which succumbs to greed, fear, lust, anger or any such tamas gunas, and indulges in acts of corruption to accumulate wealth in the country or outside. Chanakya keeps eye on conduct and life style of not only ministers, but all levels of the government officials too. Chanakya takes multi pronged approach to tackle and eradicate corruption. He knows that by establishing one department to tackle corruption problems are not going to be solved, instead will increase many fold later when that department itself becomes corrupt eventually. He relies on spying, continuous intelligence gathering, harsh punishments leading to deaths, rewards who bring to notice acts of corruptions by officials etc, promotions and rewards to who do their job righteously. Not only that, 3rd century BC, do you imagine there were clear cut rules and guidelines how to write account books, !. At that time, he knew that what impact it creates on overall economy and nation building, if sanctioned amount for projects are not utilised actually? Chanakya knows corruption is contiguous, and he tackles such problems too with well laid out and practical laws to follow at that time. Looking at the crux of the guidelines what Chanakya outlines, it seems that essence of those laws are applicable still today with more verbatim or expansion of words to suite and cover present scenarios. But, the essence remains same. He knew that in corruption free country, trade and business, entrepreneurship and industries flourishes and so overall wealth, health and security of the nation. I hope reading this book "Chanakya Niti on Corruption", will open up a window to explore further on how an Indian political guru administered this nation 3rd century BCE.

    This makes the interview process transparent and easy to prepare for because we know many of the themes they will cover and questions they will ask. Imagine if your teacher in university told you most of the questions that were going to be on the test beforehand - all you would have to do is practice. Consider this book your study guide. As a result of this structured interview process, many job seekers who do poorly in interviews simply do not spend enough time preparing. And often, the ones who do spend time preparing do not spend enough time focusing on the right things. I compiled information about the Company’s interview process, questions, and techniques that have been most successful for former applicants (current Amazon employees). This mini-guide will walk you through what it takes to get through an Amazon interview, step by step.  All you have to do is read and prepare. What’s in the book: -How to supercharge your resume and tailor keywords to get noticed by Amazon hiring managers -Tips to answer Amazon's behavioral interview questions  -A breakdown of Amazon's famous 14 leadership principles  -Understand the Amazon business model (the "flywheel") and how it relates to the interview -Common pitfalls and how to avoid them  -Perspectives from Amazon hiring managers across the world -And much more! —— “Amazon.com receives thousands of resumes every week, from talented people all over the world. Our challenge is to find the very best and recruit them into one of the many challenging positions we offer. Setting the bar high in our approach to hiring has been, and will continue to be, the single most important element of Amazon.com's success. During our hiring meetings, we ask people to consider three questions before making a decision: * Will you admire this person?
 * Will this person raise the average level of effectiveness of the group they're entering? 
 * Along what dimension might this person be a superstar?” 
 Jeff Bezos, Amazon Founder and CEO

    

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    But which ones matter to startups? Let us show you how to build your brand and sell more products in a non-spammy way with this marketing book for startups.

    Larman and Vodde have distilled their immense experience helping geographically distributed development organizations move to agile. Going beyond their previous books, they offer today's fastest, most focused guidance: "brass tacks" advice and field-proven best practices for achieving value fast, and achieving even more value as you move forward. Targeted to enterprise project participants and stakeholders, "Large-Scale Scrum" offers straight-to-the-point insights for scaling Scrum across the entire project lifecycle, from sprint planning to retrospective. Larman and Vodde help you:Implement proven Scrum frameworks for large-scale developmentsScale requirements, planning, and product managementScale design and architectureEffectively manage defects and interruptionsIntegrate Scrum into multisite and offshore projectsChoose the right adoption strategies and organizational designsThis will be the go-to resource for enterprise stakeholders at all levels: everyone who wants to maximize the value of Scrum in large, complex projects.

    The book has three parts: Principles: Part one covers the leadership principles that PMs use to lead their team to overcome adversity. When your product fails to gain traction, when your team falls apart, or when your manager gives you tough feedback—these are all opportunities to learn principles that will help you succeed. Product development: Part two covers how PMs at Facebook, Amazon, and other top companies build products. We'll walk through the end-to-end product development process— from understanding the customer problem to identifying the right product to build to executing with your team to bring the product to market. Getting the job: Part three covers how you can land a PM job and reach the interview stage at the right company. We'll prep you for the three most common types of PM interviews— product sense, execution, and behavioral—with detailed frameworks and examples for each. Hear directly from product leaders at Airbnb, Amazon, Google, and more on: How to overcome challenging situations from a VP of Product at Amazon. How to build a great product roadmap from product leaders at LinkedIn and Airbnb. How Google, Airbnb, and other top companies evaluate PM candidates from leaders at those companies. How PMs can grow their career from a Director at Instagram and Twitter. Table of Contents1. PrinciplesTake OwnershipPrioritize and ExecuteStart with WhyFind the TruthBe Radically TransparentBe Honest with Yourself2. Product DevelopmentProduct Development LoopUnderstanding the Customer ProblemSelecting a Goal MetricMission, Vision, and StrategyBuilding a Product RoadmapDefining Product RequirementsGreat Project ManagementEffective CommunicationMaking Good Decisions3. Getting the JobPreparing for the TransitionMaking the TransitionFinding the Right CompanyAcing your PM InterviewsProduct Sense InterviewExecution InterviewBehavioral InterviewYour First 30 Days4. Product Leader Interviews

    If you're one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You'll learn how to gain "quick wins" that build support, and then use the flexibility of Scrum to maximize value creation across the entire process. In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn't) be modified. Coverage includes Getting teams on board, and bringing new team members aboard after you've started Creating a "definition of done" for the team and organization Implementing the strong technical practices that are indispensable for agile success Balancing predictability and adaptability in release planning Keeping defects in check Running productive daily standup meetings Keeping people engaged with pair programming Managing culture clashes on Scrum teams Performing "emergency procedures" to get sprints back on track Establishing a pace your team can truly sustain Accurately costing projects, and measuring the value they deliver Documenting Scrum projects effectively Prioritizing and estimating large backlogs Integrating outsourced and offshored components Packed with real-world examples from Lacey's own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.

    The situations, characters and plant politics will ring true with many readers.In a cool, readable style, Andy & Me follows Tom's relationship with Andy Saito, a reclusive, retired Toyota guru whom Tom persuades to help save his plant through the teaching of the legendary Toyota Production System (TPS).On this journey, the reader learns that TPS is more than just a collection of tools; it entails a new way of thinking and behaving. Though Tom finds success -- both in his plant and in his personal life -- he learns from Andy that successful improvement is "endless and eternal."

    Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work. "Succeeding with Agile" is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement.Throughout, Cohn presents “Things to Try Now” sections based on his most successful advice. Complementary “Objection” sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes: - Practical ways to get started immediately–and “get good” fast - Overcoming individual resistance to the changes Scrum requires - Staffing Scrum projects and building effective teams - Establishing “improvement communities” of people who are passionate about driving change - Choosing which agile technical practices to use or experiment with - Leading self-organizing teams - Making the most of Scrum sprints, planning, and quality techniques - Scaling Scrum to distributed, multiteam projects - Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements - Understanding Scrum’s impact on HR, facilities, and project managementWhether you've completed a few sprints or multiple agile projects and whatever your role–manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead–this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization.

    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 book will help you get better outcomes from retrospectives and from any continuous improvement initiative. It will help you consider how best to prepare for retrospectives, generate innovative insights, achieve valuable outcomes, improve facilitation techniques, keep things fresh and maybe even how to have a bit of fun whilst doing it. This book is for anyone who undertakes continuous improvement of any sort, especially those looking to get better outcomes from retrospectives, either as a participant, facilitator, coach or manager of teams. We include ideas for people with varying levels of experience. So, whether you are just getting started with Scrum and retrospectives, or a veteran of continuous improvement looking to fine-tune or get new ideas, or if your retrospectives have become a bit stale and need re-invigorating, there are ideas in here to support you.

    More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it's a challenging role. It requires new skills--as well as a subtle understanding of when to step in and when to step back. Migrating from "command and control" to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You'll gain a deep view into the role of the agile coach, discover what works and what doesn't, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach's roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you're an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?