The document discusses the role of the business analyst in agile software development. Some key points of agile methodologies include iterative development, prioritizing individual/team interactions over processes/tools, and collaborating closely with customers. For business analysts, agile means working on just-in-time requirements in short iterations, using lightweight documentation and user stories to plan work in sprints, and adapting to change through collaboration and scope negotiation with developers. Challenges include managing requirement changes across iterations and ensuring effective communication in distributed teams.
Scaling API-first – The story of a global engineering organization
Agile and the BA
1. Reg de Silva and Benn Wheeler June 2010 Agile and the Business Analyst
2. What is Agile development? Agile is an umbrella term for several iterative and incremental software development methodologies including XP, Scrum, Kanban, and Lean
4. Agile manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
13. Story wall Story-1 As a user I want to create a record 3 Story-2 As a user I want to read a record 3 Story-3 As a user I want to update a record 2 Story-4 As a user I want to delete a record 1
19. Scope trading Story-1 As a user I want to create a record 3 Story-2 As a user I want to read a record 3 Story-3 As a user I want to update a record 2 Story-4 As a user I want to delete a record 1 Story-5 As a user I want to view the audit log 1
20. Offshore model More detailed requirements Communication tools and rules! Different time zones Common cultural understanding
21. Transition from traditional development Limited downtime – intense The right ratio of BAs to Developers & Testers Project governance fit with Agile
26. Benefits for the BA Customer satisfaction = job satisfaction One team Improved collaborationand trust with technology and business partners Your marketability!
29. Agile software development Using Agile software development – part 1 Using Agile software development – part 2 Using Agile software development – part 3 Agile development - Version One Agile manifesto Agile modeling Behaviour Driven Development definition Behaviour Driven Development Introducing BDD Kano Analysis Parking Lot Diagrams Planning Poker More information