The Power of the Agile Business Analyst: 30 Surprising Ways a Business Analyst Can Add Value to Your Agile Development Team

Book description

If the goal of an Agile project is to deliver the highest business value solution possible, why is the business user the least supported member of the Agile team?

It's good to be an Agile developer. The Agile community provides Agile developers with countless supporting resources including books, websites, forums, and conferences where Agile development issues can be raised, discussed, and jointly addressed by the group. The interesting thing is that, where Agile approaches go to great lengths to provide developers with the foundation they need to deliver high-value software solutions, there is relatively little equivalent support provided for the business users.

In most Agile methods, the business user is solely responsible for the identification, requirements gathering, clarification, and assignment of priorities for their requested system capabilities. Agile development teams rely on business users having sufficient knowledge, vision, objectivity, and time to ensure that these capabilities provide the best possible solution.

The Power of the Agile Business Analyst: 30 surprising ways a business analyst can add value to your Agile development team challenges whether Agile projects are truly positioned to deliver the highest-value business solutions without offering business users the equivalent level of support, validation, and collaboration that is provided for the Agile development team. To address this challenge, The Power of the Agile Business Analyst proposes including an Agile business analyst on the development team to provide business users with the support they need, as well as a valuable resource to assist the Agile developers in their analysis, design, testing, and implementation work throughout the project.

30 ways an Agile Business Analyst can help your team

Drawing on more than 20 years' experience as a senior business analyst and international solutions consultant, Jamie Lynn Cooke details 30 achievable ways in which Agile business analysts can increase the relevance, quality, and overall business value of your Agile projects. Read this book and learn how to:

  • Maximize the business value of your Agile solutions.
  • Leverage the skills, experience, and opportunities an Agile business analyst can bring to your project.
  • Find the most qualified Agile business analyst to complement your team.
  • Identify how an Agile business analyst can help you address the most critical challenges on your Agile project.
  • Use the strengths of an Agile business analyst to position your projects for ongoing funding and executive support.

The Power of the Agile Business Analyst also provides guidance for business analysts who want to transition their skills to work most effectively in Agile environments.

Bridge the gap between the business users and the Agile development team

The Power of the Agile Business Analyst explains how having a skilled business analyst on the Agile team provides business users with peer support for their most critical business requirements, and provides the Agile development team with a business-knowledgeable resource who is available to work hands-on with them throughout the project. These are only some of the ways in which Agile business analysts empower development teams to deliver the most successful Agile solutions.

Read this book and discover how an Agile business analyst can significantly increase the value of your solution.

Table of contents

  1. Dedication
  2. Foreword
  3. Preface
  4. About the Author
  5. Acknowledgements
  6. contents
  7. Introduction
  8. Chapter 1: What is Agile?2F
  9. Chapter 2: The Power and the Perils of Agile
    1. The lopsided process diagram
    2. The slippery slope
    3. Improving continuous improvement
  10. Chapter 3: Why Your Team Needs an Agile Business Analyst
    1. Is pairing only for developers?
    2. The disappearance of the traditional business analyst
    3. The emergence of the Agile business analyst (1/2)
    4. The emergence of the Agile business analyst (2/2)
    5. Isn't the Agile developer also the business analyst?
    6. Individual strengths in multidisciplinary teams
    7. Where does the Agile business analyst belong?
  11. Chapter 4: What are the Risks of Not Having an Agile Business Analyst?
    1. The limitations of requirements review sessions
    2. Software is only part of the solution
    3. The danger of the unquestioned business user
      1. Direct engagement between the Agile team and the business users
      2. The value of including an Agile business analyst
    4. The tyranny of proximity
    5. What to do when the business user is not available (1/2)
    6. What to do when the business user is not available (2/2)
    7. Opportunities that could be missed
  12. Chapter 5: 30 Ways for the Agile Business Analyst to Add Value to Your Project
    1. 1. Identifying and confirming user stories
    2. 6. Reviewing and refining existing business processes
    3. 7. Getting input from all relevant stakeholders
    4. 8. Managing feature lists and priorities
    5. 9. Providing input to Agile team estimation and planning
    6. 10. Researching and resolving outstanding issues
    7. 11. Assisting Agile team members in designing user interfaces
    8. 12. Analyzing data mapping, conversion, and migration requirements
    9. 13. Analyzing interface requirements for external systems
    10. 14. Investigating legacy systems
    11. 15. Identifying permissions and security requirements
    12. 16. Advising on capacity planning
    13. 17. Assisting in asset and infrastructure acquisition
    14. 18. Developing requirements, user, and/or system documentation
    15. 19. Assisting in project management reporting
    16. 20. Ensuring compliance with quality management systems
    17. 21. Documenting test plans and test cases
    18. 22. Executing system and integration tests
    19. 23. Executing preliminary acceptance tests
    20. 24. Advising on training requirements
    21. 25. Providing training services
    22. 26. Writing content for online help screens
    23. 27. Preparing release notes and known issues lists
    24. 28. Assisting in cross-organizational communication
    25. 29. Acquiring additional and ongoing project funding
    26. 30. Providing business continuity for the Agile developers
  13. Chapter 6: Getting the Right Agile Business Analyst for Your Team
    1. Building the ideal Agile business analyst
      1. Qualifications
      2. Attitude
      3. Skills (1/2)
      4. Skills (2/2)
      5. Knowledge
    2. If you are a traditional business analyst…
    3. The bottom line
  14. Chapter 7: Moving Your Agile Team Forward
    1. Where are you in the project timeline? (1/2)
    2. Where are you in the project timeline? (2/2)
    3. What are the most likely challenges?
    4. What are the natural strengths of the Agile team members?
  15. Chapter 8: More Information on Agile
    1. General information on Agile
    2. Specific Agile methodologies
      1. Overview
      2. Scrum
      3. DSDM
      4. FDD™
      5. Lean
      6. XP
      7. Kanban
      8. RUP®
      9. EssUP
      10. AUP
      11. Crystal
    3. Selected Agile case studies
  16. Author's Note on Agile Business Analysis Resources
  17. ITG Resources

Product information

  • Title: The Power of the Agile Business Analyst: 30 Surprising Ways a Business Analyst Can Add Value to Your Agile Development Team
  • Author(s): Jamie Lynn Cooke
  • Release date: October 2013
  • Publisher(s): IT Governance Publishing
  • ISBN: 9781849285056