Agile is an iterative approach to software development that has rapidly gained popularity in the IT industry as the preferred alternative to traditional project management. For business analysts, adopting an Agile approach can revolutionize working practices. It enables clearer vision and success measure definitions, better stakeholder engagement and a greater understanding of customer needs, amongst other benefits. This book provides a comprehensive introduction to Agile methodologies and explains these in the context of business analysis. It is ideal for business analysts wanting to learn and understand Agile practices, working in an Agile environment, or undertaking Agile certifications. ---\n"This book is invaluable to anyone undertaking agile analysis, illustrating that by using new techniques to supplement and extend the BA toolkit, and adopting a “just enough, just in time” philosophy, a truly agile delivery approach can be supported.'' Dr Terri Lydiard, Teal Business Solutions Ltd -- ''The complex world of Agile made relevant for BAs. Combines well-explained theory with wide-ranging practical application and offers an essential handbook for anyone involved in the Agile project world. A valuable addition to the BA toolkit.'' Sandra Leek, Lloyds Banking Group, Senior Lead Business Analyst and IIBA Business Analyst of the Year 2014 --- ''I have never understood those in the Agile community that have insisted that there is no need for an analyst role in the context of Agile projects. The project team needs access to first-hand business knowledge, combined with empowered and timely decision making but if the business representatives don’t have the experience or skills to translate their contribution to the project team, then the project will suffer. With this book, Lynda and Debra bridge this gap and help not only the business but also the Agile community, to understand why the gap exists, what can be done to address it, which existing roles can help, and how existing Agile roles and practices contribute to the solution. I highly recommend it.'' Julian Holmes, Thought Works, Principal Consultant

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) is the only globally recognized standard of practice for business analysis. Developed through a rigorous consensus-driven standards process, the BABOK® Guide incorporates the collective wisdom and experience of experts in the field from around the world. Previous editions have guided hundreds of thousands of professionals in their work, and it has been adopted by hundreds of enterprises as the basis of their business analysis practice. This latest version of the guide extends its scope beyond business analysis in projects to address agile development, business process management, business intelligence, and business architecture. This thoroughly revised and updated version includes: • A concept model that unifies ideas and terminology across business analysis disciplines. • Restructured knowledge areas to support business analysis at every level from small tactical initiatives to major business transformations. • Five perspectives covering the most prominent business analysis disciplines and demonstrating how to apply the knowledge areas in different situations. • Coverage of new business analysis techniques that have gained wide acceptance in the community. • Updated and revised content in every knowledge area and more! Whether you are considering starting a career in business analysis, or you are an experienced professional in the field,the BABOK® Guide is your key resource to help you and your stakeholders discover opportunities for business success, deliver successful organizational change, and create business value.

"If you haven't had the good fortune to be coached by a strong leader or product coach, this book can help fill that gap and set you on the path to success."- Marty CaganHow do you know that you are making a product or service that your customers want? How do you ensure that you are improving it over time? How do you guarantee that your team is creating value for your customers in a way that creates value for your business?In this book, you'll learn a structured and sustainable approach to continuous discovery that will help you answer each of these questions, giving you the confidence to act while also preparing you to be wrong. You'll learn to balance action with doubt so that you can get started without being blindsided by what you don't get right.If you want to discover products that customers love-that also deliver business results-this book is for you.About the AuthorTeresa Torres is an internationally acclaimed author, speaker, and coach. She teaches a structured and sustainable approach to continuous discovery that helps product teams infuse their daily product decisions with customer input. She’s coached hundreds of teams at companies of all sizes, from early-stage start-ups to global enterprises, in a variety of industries. She has taught over 8,500 product people discovery skills through the Product Talk Academy.What People Are Saying“Teresa Torres shows how to truly – and continuously – include customers. This is a must read for every CEO and product team out there.” - Phil Terry, Founder, Collaborative Gain; co-author, Customers Included“Teresa's work in product discovery is a constant and critical reminder that job number one for a product team is to understand who you are building for and what value you can create for them. Her methods inspire rigor similar to a workout coach - product discovery is a regular, consistent practice, that's measurable and impactful.” - Jocelyn Mangan, CEO, HimForHer“It’s no secret that regularly engaging with customers helps you discover better opportunities to serve them - yet we all struggle to do it well. This book is an indispensable guide to making this critical activity a continuous habit.” - Martin Eriksson, Co-Founder & Chairman, Mind the Product“Teresa has helped our product teams shift from a focus on outputs to delivering outcomes by helping us understand our customers better. We are building better solutions that get used more often and provide more value for our customers.” - Mike Herrick, SVP Technology, Airship“Teresa has mastered the art of helping product teams adopt a continuous cadence to their discovery work. Reading this book is like having her by your side, guiding your work, helping you find success, while developing your expertise.” - Hope Gurion, Product Leader & Team Coach, Fearless Product

You may be wondering if business analysis is the right career choice, debating if you have what it takes to be successful as a business analyst, or looking for tips to maximize your business analysis opportunities. With the average salary for a business analyst in the United States reaching above $90,000 per year, more talented, experienced professionals are pursuing business analysis careers than ever before. But the path is not clear cut. No degree will guarantee you will start in a business analyst role. What's more, few junior-level business analyst jobs exist. Yet every year professionals with experience in other occupations move directly into mid-level and even senior-level business analyst roles. My promise to you is that this book will help you find your best path forward into a business analyst career. More than that, you will know exactly what to do next to expand your business analysis opportunities.

The foremost authority on innovation and growth presents a path-breaking book every company needs to transform innovation from a game of chance to one in which they develop products and services customers not only want to buy, but are willing to pay premium prices for.How do companies know how to grow? How can they create products that they are sure customers want to buy? Can innovation be more than a game of hit and miss? Harvard Business School professor Clayton Christensen has the answer. A generation ago, Christensen revolutionized business with his groundbreaking theory of disruptive innovation. Now, he goes further, offering powerful new insights.After years of research, Christensen and his co-authors have come to one critical conclusion: our long held maxim--that understanding the customer is the crux of innovation--is wrong. Customers don't buy products or services; they "hire" them to do a job. Understanding customers does not drive innovation success, he argues. Understanding customer jobs does. The "Jobs to Be Done" approach can be seen in some of the world's most respected companies and fast-growing startups, including Amazon, Intuit, Uber, Airbnb, and Chobani yogurt, to name just a few. But this book is not about celebrating these successes--it's about predicting new ones.Christensen, Hall, Dillon, and Duncan contend that by understanding what causes customers to "hire" a product or service, any business can improve its innovation track record, creating products that customers not only want to hire, but that they'll pay premium prices to bring into their lives. Jobs theory offers new hope for growth to companies frustrated by their hit and miss efforts.This book carefully lays down the authors' provocative framework, providing a comprehensive explanation of the theory and why it is predictive, how to use it in the real world--and, most importantly, how not to squander the insights it provides.

This volume presents a detailed explanations of business analysis concepts, terms, tasks, and techniques, and includes examples to help readers understand how to apply them to real-world situations. It also delineates the key activities that are core to the BA role and the diverse range of activities analysts perform based on their career competency level, ranging from problem solving and identification of business opportunities, to complex systems thinking and solution development, to strategic planning and change management. It is a must-have reference for BA generalists, specialists, and hybrids at every career level and industry segment or perspective.

“Build, Measure and Learn” as Steve Blank says: is much more elaborate than putting software into production to see if it works. The Lean Startup movement is very promising, but for many teams it ends up translating into an important question: ”Yeah, but what to build ?”“In ThoughtWorks, our response has been a process called an inception. We gather together a good sample of the people who will be affected by the product and have an intensive session to set an initial direction, using a series of exercises focusing on collaboration and the capture of broad goals. We don't attempt a detailed specification, as that is exactly the kind of thing that becomes out of date as soon as code hits production. But we do want to understand what kind of outcomes we are hoping for, the features that we think will drive these outcomes, and how to assess the effectiveness of our product.With The Lean Inception, Paulo has captured his experience in running these inceptions over the last decade. In particular it's focused on his work to boil the inception down to its essence, concentrating the activity on a single, if very intensive, week of work. Paulo shares how he makes this work, through writing a product vision, capturing personas, understanding the user journeys, and developing high-level features. The result isn't a detailed plan of work, which we find quickly rots into irrelevance. It is a guiding set of goals to set us off in the right direction. It doesn't plan out a final product, with all the features that our users will need, instead it focuses on an initial product that we can release and learn from - the Minimum Viable Product. “ – Martin Fowler, Chief Cientist at ThoughtWorks

Business Analysis for Practitioners: A Practice Guide provides practical resources to tackle the project-related issues associated with requirements and business analysis—and addresses a critical need in the industry for more guidance in this area. The practice guide begins by describing the work of business analysis. It identifies the tasks that are performed, in addition to the essential knowledge and skills needed to effectively perform business analysis on programs and projects.

From inside Google Ventures, a unique five-day process for solving tough problems, proven at thousands of companies in mobile, e-commerce, healthcare, finance, and more.Entrepreneurs and leaders face big questions every day: What’s the most important place to focus your effort, and how do you start? What will your idea look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution?Now there’s a surefire way to answer these important questions: the Design Sprint, created at Google by Jake Knapp. This method is like fast-forwarding into the future, so you can see how customers react before you invest all the time and expense of creating your new product, service, or campaign.In a Design Sprint, you take a small team, clear your schedules for a week, and rapidly progress from problem, to prototype, to tested solution using the step-by-step five-day process in this book.A practical guide to answering critical business questions, Sprint is a book for teams of any size, from small startups to Fortune 100s, from teachers to nonprofits. It can replace the old office defaults with a smarter, more respectful, and more effective way of solving problems that brings out the best contributions of everyone on the team—and helps you spend your time on work that really matters.

The role of the business analyst is to formulate options for a way forward and produce business cases setting out conclusions and recommendations. This professional discipline requires the widest possible array of tools and the ability to use each when and where it is needed. The new edition provides 99 possible techniques and applies them within a framework of stages. It complements Business Analysis (ed Debra Paul, Donald Yeates and James Cadle), also published by BCS, and offers a more detailed description of the techniques used in business analysis, together with practical advice on their application. This book will be of enormous benefit to business analysts, managers and to students of information systems and business strategy.

“This book helps teams that are pursuing backlog success to determine exactly how to build a cross functional, successful, and realistic backlog that delivers value, collects evidence, and updates the prioritization and the work being done in each Sprint, objectively and in a customer-centered way.” - Jeff Gothelf\nAgile teams must constantly deal with questions and uncertainties as they develop their product. These include managing a Product Backlog, understanding the customer’s needs, determining how to build something that has value, and setting appropriate priorities.\nMoved by the need to clarify this often complex path, Fábio Aguiar developed the Product Backlog Building method (PBB). Together with Paulo Caroli, creator of the Lean Inception method, they present a practical guide for those who want to build a successful product, specifically by creating and refining the backlog.\nBy incorporating PBB into your product development flow, and by following the steps presented in this book, you and your team will be able to: Develop a shared understanding of the product needs. Facilitate the writing of user stories. Structure the granularity of backlog items. Prioritize the items of greatest importance to the product and to the customer. Improve teamwork and collaboration.

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

- How can you drive the thinking on what to develop, why and how to do it — leveraging the insights from both team and stakeholders — all the way from idea to deploy?- This book tries to answer the above question. We interviewed over 300 Product Managers to understand how they work and collaborate around feature development, what problems they face, and the many approaches to solving those problems.- "Epic alignment" describes four broad approaches that we saw help Product Managers excel.What you'll learn:- How to drive product development towards impact based on research- How to use user stories as a shared language to align your entire team- How to write feature documents that drive joint understanding and act as a single source of truth- How to tackle the massive amounts of decisions needed for every epic

What's Inside? \nLearn how to master requirements elicitation, analysis and documentation. \nBuild-up your project management and lean six sigma skill sets. \nInterview questions and cheat sheets.\nThorough explanation of SDLC and UML methodologies\nReal-time project situations and examples. \nStep-by-step guide on facilitating sessions. \nHands-on guide to the business analysis tasks. \nOn-the-job support. \nIntroduction to SQL. \nReal-time templates that you can use in your projects now. \nYour shortcut to a Business Analyst job.\n\n3D Business Analysis is a unique fusion of three distinct specialties - business analysis (BA),project management (PM) and lean six sigma (LSS) - with traditionally separate skill sets and career paths. However, when the components of these skill sets are analyzed and understood, a clear overlap emerges, and if used together, they provide the BA with the necessary concepts, theories and terminologies to allow him or her to communicate more effectively with stakeholders using their specific language, realize expectations and add more value to the organization.

Written with special attention to the challenges facing the IT business analyst, The Agile Business Analyst is a fresh, comprehensive introduction to the concepts and practices of Agile software development. It is also an invaluable reference for anyone in the organization who interacts with, influences, or is affected by the Agile development team. Business analysts will learn the key Agile principles plus valuable tools and techniques for the transition to Agile, including: \n\nCard writing Story decomposition How to manage cards in an Agile workflow How to successfully respond to challenges about the value of the BA practice (with an “elevator pitch” for quick reference) \n\nScrum masters, iteration managers, product owners, and developers who have been suddenly thrust into a work environment with a BA will find answers to the many questions they’re facing: \nWhat does a BA actually do? What’s their role on the team? What should I expect from a BA? How and when should I involve a BA, and what are the limits of their responsibility? How can they help my team increase velocity and/or quality? \n\nPeople managers and supervisors will discover: \nHow the BA fits into the Agile team and SDLC Crucial skills and abilities a BA will need to be successful in Agile How to get the team and the new BA off on the right foot How to explain the BA’s value proposition to others How adding a BA can solve problems in an established team \nExecutives and directors will find answers to critical questions: \nIn an Agile world, are BAs a benefit or just a cost to my organization? How do I get value from a BA in the transition to Agile? Can I get more from my development team by using the BA as a “force multiplier”? What expectations should I be setting for my discipline managers? \n With a foreword by Barbara Carkenord, The Agile Business Analyst is a must-read for any analyst working in an Agile environment. “Fresh insights, practical recommendations, and detailed examples, all presented with an entertaining and enjoyable style. Leyton shares his experience, mentoring his reader to be a more effective analyst. He has hit a home run with this book!” --Barbara Carkenord, Director, Business Analysis/RMC Learning Solutions “Leyton does a great job explaining the value of analysis in an Agile environment. If you are a business-analysis practitioner and need help figuring out how you add value to your team, you’ll find this book valuable.” --Kupe Kupersmith, President, B2T Training

This book undertakes to marry the concepts of "Concept Mapping" with a "Design Thinking" approach in the context of business analysis. While in the past a lot of attention has been paid to the business process side, this book now focusses information quality and valuation, master data and hierarchy management, business rules automation and business semantics as examples for business innovation opportunities. The book shows how to take "Business Concept Maps" further as information models for new IT paradigms. In a way this books redefines and extends business analysis towards solutions that can be described as business synthesis or business development. Business modellers, analysts and controllers, as well as enterprise information architects, will benefit from the intuitive modelling and designing approach presented in this book. The pragmatic and agile methods presented can be directly applied to improve the way organizations manage their business concepts and their relationships.\n"This book is a great contribution to the information management community. It combines a theoretical foundation with practical methods for dealing with important problems. This is rare and very useful. Conceptual models that communicate business reality effectively require some degree of creative imagination. As such, they combine the results of business analysis with communication design, as is extensively covered in this book."\nDr. Malcolm Chisholm, President at AskGet.com Inc.\n“Truly understanding business requirements has always been a major stumbling block in business intelligence (BI) projects. In this book, Thomas Frisendal introduces a powerful technique―business concept mapping―that creates a virtual mind-meld between business users and business analysts. Frisendal does a wonderful explaining and demonstrating how this tool can improve the outcome of BI and other development projects ."\nWayne Eckerson, executive director, BI Leadership Forum

As a Quick Guide to Business Analysis, the book explains international techniques and tools such as: - User stories - Use cases - MVP (minimum viable product) - Requirements documents - User interface prototypes - Lean UX (user experience) design - Vision and scope documents - Business cases - Feasibility analysis - Personas and user profiles - Product backlogs - Usability tests - Value proposition that can be used in developing and releasing: - Software, - Business solutions, - Technological products, - Mobile applications, - E-businesses and, - Business processes within tight project deadlines by applying "lean" principles. A real life case study with sample project documents and diagrams is used to more practically explain these international tools, techniques, and lean principles to a broad range of practitioners, including: - Business analysts, systems analysts, developers and project managers - Entrepreneurs, product owners and product managers - Consultants, UX designers and marketing specialists - C-suite executives, investors and managers of companies of all sizes.

Whether you are a professional with twenty years of experience, or a new analyst – and whether your projects are short two-week efforts or multi-million dollar corporate initiatives – the Event-based analysis approach covered in this book is for you. This book is about “agile” business system analysis; and how to create a modern, useful business requirements specification really fast, without the tedious constraints of the past, and without the risk often associated with the term “agile”. “Agile” business system analysis is about how to find the exact, specific questions to ask your clients and users (subject-matter experts) – in the specific context of your project – and a way of doing the highest quality analysis in the fastest way possible, without chaos. It’s about business-based analysis suitable to building the complex integrated systems for the 21st century. It’s about you, and how to find and specify the business requirements for a project successfully. And fast. This book is not a a silver bullet nor is it a magic wand to wave over troubled legacy systems. This is a book about getting the business requirements for a system specified fast and right the very first time – without engaging in an archaeological dig that takes forever. “So, is this more of the Same Old Stuff,” you might ask, “but with different packaging?” No, this is not more of the Same Old Stuff (with – you guessed it – the Same Old Results). But, find out for yourself. Try the event-based analysis approach described in this book – you'll never look back. Admittedly, “agile” means a lot of different things to different people. There will be some who seek instant answers and instant tools. But the only tools that count in the area of business system analysis is your ability to ask the right questions of your subject-matter experts (clients and users), in the context of your specific project, and to properly document their responses – but without taking forever. This book will show you how to do it – with precision and accuracy.

This book covers the area of product and process modelling via a case study approach. It addresses a wide range of modelling applications with emphasis on modelling methodology and the subsequent in-depth analysis of mathematical models to gain insight via structural aspects of the models. These approaches are put into the context of life cycle modelling, where multiscale and multiform modelling is increasingly prevalent in the 21st century. The book commences with a discussion of modern product and process modelling theory and practice followed by a series of case studies drawn from a variety of process industries. The book builds on the extensive modelling experience of the authors, who have developed models for both research and industrial purposes. It complements existing books by the authors in the modelling area. Those areas include the traditional petroleum and petrochemical industries to biotechnology applications, food, polymer and human health application areas. The book highlights to important nature of modern product and process modelling in the decision making processes across the life cycle. As such it provides an important resource for students, researchers and industrial practitioners. Ian Cameron is Professor in Chemical Engineering at the University of Queensland with teaching, research, and consulting activities in process systems engineering. He has a particular interest in process modelling, dynamic simulation, and the application of functional systems perspectives to risk management, having extensive industrial experience in these areas. He continues to work closely with industry and government on systems approaches to process and risk management issues. He received his BE from the University of New South Wales (Australia) and his PhD from imperial College London. He is a Fellow of IChemE. Rafiqul Gani is a Professor of Systems Design at the Department of Chemical and Biochemical Engineering, Technical University of Denmark, and the director of the Computer Aided Product-Process Engineering Center (CAPEC). His research interests include the development of computer-aided methods and tools for modelling, property estimation and process-product synthesis and design. He received his BSc from Bangladesh University of Engineering and Technology in 1975, and his MSc in 1976 and PhD in 1980 from Imperial College London. He is the editor-in-chief of Computers and Chemical Engineering journal and Fellow of IChemE as well as AIChE.\n\nProduct and process modelling; a wide range of case studies are covered\nStructural analysis of model systems; insights into structure and solvability\nAnalysis of future developments; potential directions and significant research and development problems to be addressed\n

Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. 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. \nDescribes 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. \n 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.

Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. This guide provides software developers with a nuts-and-bolts tutorial for writing use cases. It covers introductory, intermediate, and advanced concepts, and is suitable for all knowledge levels.

The Agile Extension to the BABOK(R) Guide (Agile Extension) version 2 describes the benefits, activities, tasks, skills, and practices required for effective agile business analysis with a constant focus on delivering business value.\nThe Agile Extension version 2: \ndescribes the agile mindset and positions agile business analysis beyond software development introduces a 3-tier rolling planning model to help organizations, teams, and practitioners deliver greater business value incorporates the Business Analysis Core Concept Model(TM) (BACCM(TM)) details the seven principles of agile business analysis \nThe Agile Extension to the BABOK(R) Guide is an ongoing initiative of Agile Alliance and the International Institute of Business Analysis(TM) (IIBA(R)) since 2009. The Agile Extension provides guidance for Agile practitioners or anyone interested in leveraging effective Agile business analysis to create better business outcomes that add real business and customer value