This is Writers On Writing – An Author’s Guide, where your favorite authors share their secrets in the ultimate guide to becoming – and being – an author. In this first volume you’ll find in-depth essays from authors such as Jack Ketchum, Brian Hodge, Mercedes M. Yardley, Tim Waggoner, Jasper Bark, Kevin Lucia, Monique Snyman, Todd Keisling, and Dave-Brendon de Burgh. Edited by Joe Mynhardt. “The Infrastructure of the Gods: 11 Signposts for Going all the Way” by Brian Hodge “The Writer’s Purgatory: Between Finishing the First Draft and Submitting the Manuscript” by Monique Snyman “Why Rejection is Still Important” by Kevin Lucia “Real Writers Steal Time” by Mercedes M. Yardley “What Right Do I Have to Write” by Jasper Bark “Go Pace Yourself” by Jack Ketchum “A Little Infusion of Magic” by Dave-Brendon de Burgh “Never Look Away: Confronting Your Fears in Fiction” by Todd Keisling “Once More With Feeling” by Tim Waggoner Writers On Writing is an ongoing series of 15,000 to 20,000 word eBooks, with original ‘On Writing’ essays by writing professionals. A new edition will be launched every few months. Future volumes will include essays by the likes of Kealan Patrick Burke, Richard Thomas, Mark Scioneaux, Rena Mason, J.G. Faherty, William Meikle, Lucy A. Snyder, Kate Jonez, Chantal Noordeloos, Taylor Grant, Gary McMahon, Lori Michelle, Robert W. Walker, Brian Kirk, Lisa Morton, Lynda E. Rucker, Maria Alexander, and many more. Writers On Writing give young authors the guidance they need, but has advice for all authors, from the interested newbie to the seasoned veteran (sounds delicious, right?). This ongoing series of essays on the craft of writing will include all topics related to writing fiction, including: The Basics Plot & Structure Voice Theme POV Characterization Dialogue Narrative Creating a bond with your reader Pacing Advanced writing and plotting techniques Writer’s block Marketing Branding Publishing Self-publishing Healthy habits Bad habits The Writer’s Life eBook formatting Paperback formatting Amazon keywords Writing blurbs and descriptions Cover design & layout Productivity The Classics Short stories Poetry The Writing Process Show don’t Tell Self-editing Proofreading Building a solid career Targeting a specific genre Genre Fiction Literary Fiction Sharpening your writing skills Making every word count Deadlines Putting together an Anthology Working with other artists Collaborating Grammar Punctuation Writing for a career Treating it as a business Running a small press Financing your career Keeping track of your royalties Staying motivated Writing movies Writing comics Writing games Building a fan-base Online presence Newsletters Podcasting Author interviews Media appearances Websites Blogging And so much more&hel

    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

    In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies.Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile.Using the techniques in Agile Estimating and Planning , you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include:Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days--and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.

    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?

    In a short time, it can enhance your skills in reading, writing, learning, note taking, brainstorming, planning, productivity, and so much more.

    

    But creating an environment for creative thinking and innovation can be a daunting challenge. How can you make it happen at your company? The answer may surprise you: gamestorming.This book includes more than 80 games to help you break down barriers, communicate better, and generate new ideas, insights, and strategies. The authors have identified tools and techniques from some of the world's most innovative professionals, whose teams collaborate and make great things happen. This book is the result: a unique collection of games that encourage engagement and creativity while bringing more structure and clarity to the workplace. Find out why -- and how -- with Gamestorming.Overcome conflict and increase engagement with team-oriented gamesImprove collaboration and communication in cross-disciplinary teams with visual-thinking techniquesImprove understanding by role-playing customer and user experiencesGenerate better ideas and more of them, faster than ever beforeShorten meetings and make them more productiveSimulate and explore complex systems, interactions, and dynamicsIdentify a problem's root cause, and find the paths that point toward a solution

    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.

    Easy reading and enjoyable.." - John P Sam's trousers were round his ankles. The microwaved chicken - long past its sell-by date - had made a hasty exit. He was down a ditch in the middle of nowhere, and there weren't any tissues. Suzy had dumped him. Things weren't going well. He was only one wipe away from his life changing forever when he found a blue IKEA bag packed with banknotes. Gary wants to kill him. So does Vlad. Ashton wants to paint him naked and then there's the Contessa. Suzy isn't certain they've broken up. One thing’s for sure: Sam's life has been turned upside down.

    

    New Zealand needed just one more win. Oracle ultimately beat back the odds in what's been called the greatest comeback in sport. But was it? G. Bruce Knecht set out to investigate how Oracle turned things around and, most particularly, the source of extra horsepower that seemed to come from nowhere during the final races. What he discovered was that the team was using a sailing technique that was prohibited under the rules. The Comeback is a pulse-pounding account of Oracle's desperate stop-at-nothing campaign.G. Bruce Knecht, a former staff reporter and foreign correspondent for The Wall Street Journal, is the author of three books, including The Proving Ground: The Inside Story of the 1998 Sydney to Hobart Race. Larry Ellison was a major character in that book as well and it explains how his experience in the race led to his pursuit of the America's Cup. A sailor himself, Knecht raced across the Atlantic in 2005 on the yacht that broke the 100-year-old transatlantic race record.Cover design by Charles Rue Woods.

    After the unexpected death of their mother, three young sisters -- Draya, Yandy and Charlie, are faced with some serious challenges. With inheriting their mother's debts and no clear direction as to what the future will bring, the sisters are forced to come up with clever ways to keep their heads above water. Realizing the power and sway they can hold over a man's heart and pockets, the girls set out to become FINESSE QUEENS.Read this breakout urban romance drama by best selling author Quan Millz. You won't be disappointed.

    Operating from camps in places like Kontum and Dak To, Special Forces recon men risked their lives behind enemy lines on the Ho Chi Minh Trail in Laos and Cambodia, conducting missions whose detection often meant death or something worse. Officially, they did not exist. Their government denied that they were operating in “neutral” countries; Hanoi denied the very existence of the Trail. If killed or captured in Laos or Cambodia, the Green Berets would be reported MIA or KIA—in Vietnam. They fought for each other and for their honor as soldiers. It is 1970. The United States Government is seeking a way out of the war “with honor” via a face-saving program called “Vietnamization.” This is the story of the fate of the recon men and the missions they conducted while highly skilled and motivated NVA hunter-killer teams pursued them on the enemy’s home turf. A recon team discovers a choke point on the enemy’s line of communication. For every day the Trail is blocked, enemy support of forces in the south is set back a month, giving South Vietnam a leg up. The special operators in Kontum are given the mission to do just that. There is a rub; the American president and his government must have “plausible deniability.” Therein lies the legacy of lies. “Very few authors have captured the action, intrigue and backstory of the secret missions as well as Colonel Gole does in ‘Legacy of Lies.’ A must read for those seeking the precursor to today’s military support to sensitive activities.” —Michael S. Repass, Major General, US Army (Retired) Special Forces “Gole’s novel is Fantastic! The best part, the top to bottom approach—from the White House, JCS, CINCPAC, MACV, down through SOG, right to the One-Zero firing tracers to mark his position for Covey.” —Colonel, USAF, (Ret) Tom Yarborough, author and decorated Covey pilot for SOG

    But what happens when a friendship fades, and people go their separate ways? Does it mean they won’t see each other again or does it make the friendship stronger when they reunite? Lexi is a college graduate who thought Frankie was the love of her life; until she met someone else. He swept her off her feet and promised to love her forever. Unfortunately, with every new person you meet, there’s always a hidden agenda. Frankie promised to marry Lexi when they were younger, but as fate would have it, nothing went as planned. She left for school while he stayed back and did his own thing. His new girlfriend, Crystal, has plans of her own for Frankie and will make sure nothing or no one stands in her way of getting him; including his long lost love Lexi. Take a journey with the characters you love to hate and see if Luvin' A Young Beast is everything it’s cracked up to be.

    When she loses the love of her life to the streets, she vows to never love a dope boy again, but some promises are meant to be broken…. Demetrius is a product of the streets and has spent the last five years in jail because enough was never enough. When he is released from prison, he tries hard to turn his life around, but as the saying goes…old habits die hard. Only settling for jump offs, he is mesmerized when he meets Kamora and instantly makes up his mind that he will do whatever it takes to win her over. Will Kamora be able to keep the promise that she made to herself after she meets the charming and persistent Demetrius? Will Demetrius be able to leave his dope boy ways alone to get Kamroa or will he be forever tied to the streets?