0%

Book Description

Now in its second edition, The Power of the Agile Business Analyst has expanded to include new Agile methods that have emerged or gained prominence since the first edition.
  • Buy this book to learn how to revolutionise your Agile development and increase the value and relevancy of your project outcomes.
  • Learn 30 realistic, achievable ways that an Agile business analyst can increase project efficiency, add value and improve quality.
  • Find out how an Agile business analyst bridges the gap between the needs of the business and the resources of the development team.
  • Now updated with current Agile methods, to support emerging and established business analysts to adapt to new trends.
30 ways an Agile business analyst can help

Drawing on her extensive experience, Jamie proposes a new role for Agile projects: The Agile business analyst. She details 30 achievable ways that such a role will increase relevance, quality and overall business value, and provide business users with crucial support. The Agile business analyst is also a boon to the development team, being a ready source of business knowledge and ensuring that project outcomes align with requirements.

This book has been updated to:
  • Incorporate behaviour-driven development into the work that the business analyst does to support interface design;
  • Align the programme management strategies of the Scaled Agile Framework (SAFe) to encourage cross-organisational communication and participation;
  • Include full updates throughout the Qualifications section in ‘Getting the Right Agile Business Analyst for Your Team’; and
  • Provide Agile updates, bringing the book back into line with current methods
  • .
Support your Agile business user for better project outcomes.

Table of Contents

  1. Cover
  2. Title
  3. Copyright
  4. Foreword
  5. Preface
  6. Author
  7. Acknowledgements
  8. Contents
  9. Introduction
  10. Chapter 1: What is Agile?
  11. Chapter 2: The power and perils of Agile
    1. The lopsided process diagram
    2. The slippery slope
    3. Improving continuous improvement
  12. 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
    4. Isn’t the Agile developer also the business analyst?
    5. Individual strengths in multidisciplinary teams
    6. Where does the Agile business analyst belong?
  13. 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
    4. The tyranny of proximity
    5. What to do when the business user is not available
    6. Opportunities that could be missed
  14. Chapter 5: 30 ways for the Agile business analyst to add value to your project
  15. Chapter 6: Getting the right Agile business analyst for your team
    1. Building the ideal Agile business analyst
    2. If you are a traditional business analyst…
    3. The bottom line
  16. Chapter 7: Moving your Agile team forward
  17. Chapter 8: More information on Agile
    1. General information on Agile
    2. Specific Agile methodologies and practices
    3. Industry research on Agile
    4. Selected Agile case studies
  18. Author’s note on Agile business analysis resources
  19. Further Reading
3.140.198.43