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