Bridging the Communication Gap is a book about improving communication between customers, business analysts, developers and testers on software projects, especially by using specification by example and agile acceptance testing. These two key emerging software development practices can significantly improve the chances of success of a software project. They ensure that all project participants speak the same language, and build a shared and consistent understanding of the domain. This leads to better specifications, flushes out incorrect assumptions and ensures that functional gaps are discovered before the development starts. With these practices in place you can build software that is genuinely fit for purpose.
Describes a method of effectively specifying, testing, and delivering software, covering such topics as documentation, process patterns, and automation, along with case studies from a variety of firms.
Author: Jeff Patton
Publisher: "O'Reilly Media, Inc."
Release Date: 2014-09-05
Genre: Business & Economics
User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features. Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why. Get a high-level view of story mapping, with an exercise to learn key concepts quickly Understand how stories really work, and how they come to life in Agile and Lean projects Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery Prepare your stories, pay attention while they’re built, and learn from those you convert to working software
This book will help you write better stories, spot and fix common issues, split stories so that they are smaller but still valuable, and deal with difficult stuff like crosscutting concerns, long-term effects and non-functional requirements. Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders. Who is this book for? This is a book for anyone working in an iterative delivery environment, doing planning with user stories. The ideas in this book are useful both to people relatively new to user stories and those who have been working with them for years. People who work in software delivery, regardless of their role, will find plenty of tips for engaging stakeholders better and structuring iterative plans more effectively. Business stakeholders working with software teams will discover how to provide better information to their delivery groups, how to set better priorities and how to outrun the competition by achieving more with less software. What's inside? Unsurprisingly, the book contains exactly fifty ideas. They are grouped into five major parts: - Creating stories: This part deals with capturing information about stories before they get accepted into the delivery pipeline. You'll find ideas about what kind of information to note down on story cards and how to quickly spot potential problems. - Planning with stories: This part contains ideas that will help you manage the big-picture view, set milestones and organise long-term work. - Discussing stories: User stories are all about effective conversations, and this part contains ideas to improve discussions between delivery teams and business stakeholders. You'll find out how to discover hidden assumptions and how to facilitate effective conversations to ensure shared understanding. - Splitting stories: The ideas in this part will help you deal with large and difficult stories, offering several strategies for dividing them into smaller chunks that will help you learn fast and deliver value quickly. - Managing iterative delivery: This part contains ideas that will help you work with user stories in the short and mid term, manage capacity, prioritise and reduce scope to achieve the most with the least software. About the authors: Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010. David Evans is a consultant, coach and trainer specialising in the field of Agile Quality. David helps organisations with strategic process improvement and coaches teams on effective agile practice. He is regularly in demand as a conference speaker and has had several articles published in international journals.
Author: Mark Denne
Publisher: Prentice Hall Professional
Release Date: 2003
- Opens the black box of methodologies and demonstrates that software development is fundamentally a value creation process - Covers new and radical approaches to software development that respond to business demands for shorter investment periods and increased agility - Provides software engineers tools for understanding enterprise-level value creation and managing financial objectives
Innovation Through Understandingsm The toughest part of innovation? Accurately predicting what customers want, need, and will pay for. Even if you ask them, they often can’t explain what they want. Now, there’s a breakthrough solution: Innovation Games. Drawing on his software product strategy and product management consulting experience, Luke Hohmann has created twelve games that help you uncover your customers’ true, hidden needs and desires. You’ll learn what each game will accomplish, why it works, and how to play it with customers. Then, Hohmann shows how to integrate the results into your product development processes, helping you focus your efforts, reduce your costs, accelerate time to market, and deliver the right solutions, right from the start. Learn how your customers define success Discover what customers don’t like about your offerings Uncover unspoken needs and breakthrough opportunities Understand where your offerings fit into your customers’ operations Clarify exactly how and when customers will use your product or service Deliver the right new features, and make better strategy decisions Increase empathy for the customers’ experience within your organization Improve the effectiveness of the sales and service organizations Identify your most effective marketing messages and sellable features Innovation Games will be indispensable for anyone who wants to drive more successful, customer-focused product development: product and R&D managers, CTOs and development leaders, marketers, and senior business executives alike.
Humans vs Computers is a book about ordinary people caught between wrong assumptions and computer bugs. You'll read about humans who are invisible to computers, how a default password caused a zombie apocalypse and why airlines sometimes give away free tickets. This is also a book on how to prevent, avoid and reduce the impact of such problems.
Author: David J. Anderson
Publisher: Prentice Hall Professional
Release Date: 2003-09-17
A breakthrough approach to managing agile software development, Agile methods might just be the alternative to outsourcing. However, agile development must scale in scope and discipline to be acceptable in the boardrooms of the Fortune 1000. In Agile Management for Software Engineering, David J. Anderson shows managers how to apply management science to gain the full business benefits of agility through application of the focused approach taught by Eli Goldratt in his Theory of Constraints. Whether you're using XP, Scrum, FDD, or another agile approach, you'll learn how to develop management discipline for all phases of the engineering process, implement realistic financial and production metrics, and focus on building software that delivers maximum customer value and outstanding business results.Coverage includes: Making the business case for agile methods: practical tools and disciplines How to choose an agile method for your next project Breakthrough application of Critical Chain Project Management and constraint-driven control of the flow of value Defines the four new roles for the agile manager in software projects—and competitive IT organizations Whether you're a development manager, project manager, team leader, or senior IT executive, this book will help you achieve all four of your most urgent challenges: lower cost, faster delivery, improved quality, and focused alignment with the business.
Author: Mike Cohn
Publisher: Addison-Wesley Professional
Release Date: 2004-03-01
Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.
A pragmatic companion guide to your Agile journey Key Features Make your team Agile by implementing industry-standard Agile techniques Assess scope, scale up efficiently Create the correct roles and identify the right candidates for your team Finish your projects faster and stay ahead of the curve Book Description This book will help you overcome the common challenges you’ll face when transforming your working practices from waterfall to Agile. Each chapter builds on the last, starting with easy-to-grasp ways to get going with Agile. Next you’ll see how to choose the right Agile framework for your organization. Moving on, you’ll implement systematic product delivery and measure and report progress with visualization. Then you’ll learn how to create high performing teams, develop people in Agile, manage in Agile, and perform distributed Agile and collaborative governance. At the end of the book, you’ll discover how Agile will help your company progressively deliver software to customers, increase customer satisfaction, and improve the level of efficiency in software development teams. What you will learn Create a solid foundation that gives your team an Agile jumpstart Understand how to select and evolve practices to increase your team’s agility Use experiments to accelerate your team’s understanding Fine-tune your approach by incorporating aspects of Lean and Lean Startup Know how to foster an environment of continuous improvement and learning that will become self-sustaining Who this book is for If you’re a software developer or a project manager with little to no experience of Agile, but you want to efficiently implement it, this is the book for you.
This book is for cross-functional teams working in an iterative delivery environment, planning with user stories and testing frequently changing software under tough time pressure. This book will help you test your software better, easier and faster. Many of these ideas also help teams engage their business stakeholders better in defining key expectations and improve the quality of their software products.
Author: Steven L. Goldman
Publisher: Van Nostrand Reinhold Company
Release Date: 1995
Genre: Business & Economics
It is becoming clear today that most of the management truisms that have guided executives and business educators for two generations no longer work. This book, written by three internationally recognized authorities on global competitiveness, is designed to help any business - large or small - come to terms with change and develop effective, profit-centered strategies. Clear, real-world examples are used to describe what it takes for companies and individuals to become "agile" - how they can thrive in a competitive environment of constant, unpredictable change. The book is the product of the authors' extensive research in cooperation with industry and government leaders that resulted in the influential 1991 report, 21st Century Manufacturing Enterprise Strategy. This book presents an updated and expanded vision of agile competition, which promises to affect life in the 21st century as profoundly as mass production-based competition affected life in the 20th century. By focusing on practice rather than on theory, the book describes in detail how this new form of competition is rapidly differentiating winners from losers, not just in the U.S. but around the world.
Author: Scott W. Ambler
Publisher: IBM Press
Release Date: 2012-05-31
Master IBM’s Breakthrough DAD Process Framework for Succeeding with Agile in Large, Complex, Mission-Critical IT Projects It is widely recognized that moving from traditional to agile approaches to build software solutions is a critical source of competitive advantage. Mainstream agile approaches that are indeed suitable for small projects require significant tailoring for larger, complex enterprise projects. In Disciplined Agile Delivery, Scott W. Ambler and Mark Lines introduce IBM’s breakthrough Disciplined Agile Delivery (DAD) process framework, which describes how to do this tailoring. DAD applies a more disciplined approach to agile development by acknowledging and dealing with the realities and complexities of a portfolio of interdependent program initiatives. Ambler and Lines show how to extend Scrum with supplementary agile and lean strategies from Agile Modeling (AM), Extreme Programming (XP), Kanban, Unified Process (UP), and other proven methods to provide a hybrid approach that is adaptable to your organization’s unique needs. They candidly describe what practices work best, why they work, what the trade-offs are, and when to consider alternatives, all within the context of your situation. Disciplined Agile Delivery addresses agile practices across the entire lifecycle, from requirements, architecture, and development to delivery and governance. The authors show how these best-practice techniques fit together in an end-to-end process for successfully delivering large, complex systems--from project initiation through delivery. Coverage includes Scaling agile for mission-critical enterprise endeavors Avoiding mistakes that drive poorly run agile projects to chaos Effectively initiating an agile project Transitioning as an individual to agile Incrementally building consumable solutions Deploying agile solutions into complex production environments Leveraging DevOps, architecture, and other enterprise disciplines Adapting your governance strategy for agile projects Based on facts, research, and extensive experience, this book will be an indispensable resource for every enterprise software leader and practitioner--whether they’re seeking to optimize their existing agile/Scrum process or improve the agility of an iterative process.
“Collaboration Explained is a deeply pragmatic book that helps agile practitioners understand and manage complex organizational and team dynamics. As an agile coach, I’ve found the combination of straightforward advice and colorful anecdotes to be invaluable in guiding and focusing interactions with my teams. Jean’s wealth of experience is conveyed in a carefully struck balance of reference guides and prose, facilitating just-in-time learning in the agile spirit. All in all, a superb resource for building stronger teams that’s fit for agile veterans and neophytes alike.” —Arlen Bankston, Lean Agile Practice Manager, CC Pace “If Agile is the new ‘what,’ then surely Collaboration is the new ‘how.’ There are many things I really like about Jean’s new book. Right at the top of the list is that I don’t have to make lists of ideas for collaboration and facilitation anymore. Jean has it all. Not only does she have those great ideas for meetings, retrospectives, and team decision-making that I need to remember, but the startling new and thought-provoking ideas are there too. And the stories, the stories, the stories! The best way to transfer wisdom. Thanks, Jean!” —Linda Rising, Independent Consultant The Hands-On Guide to Effective Collaboration in Agile Projects To succeed, an agile project demands outstanding collaboration among all its stakeholders. But great collaboration doesn’t happen by itself; it must be carefully planned and facilitated throughout the entire project lifecycle. Collaboration Explained is the first book to bring together proven, start-to-finish techniques for ensuring effective collaboration in any agile software project. Since the early days of the agile movement, Jean Tabaka has been studying and promoting collaboration in agile environments. Drawing on her unsurpassed experience, she offers clear guidelines and easy-to-use collaboration templates for every significant project event: from iteration and release planning, through project chartering, all the way through post-project retrospectives. Tabaka’s hands-on techniques are applicable to every leading agile methodology, from Extreme Programming and Scrum to Crystal Clear. Above all, they are practical: grounded in a powerful understanding of the technical, business, and human challenges you face as a project manager or development team member. · Build collaborative software development cultures, leaders, and teams · Prepare yourself to collaborate—and prepare your team · Define clear roles for each participant in promoting collaboration · Set your collaborative agenda · Master tools for organizing collaboration more efficiently · Run effective collaborative meetings—including brainstorming sessions · Promote better small-group and pair-programming collaboration · Get better information, and use it to make better decisions · Use non-abusive conflict to drive positive outcomes · Collaborate to estimate projects and schedules more accurately · Strengthen collaboration across distributed, virtual teams · Extend collaboration from individual projects to the entire development organization