Business Analysis for Agile Projects

Concepts

The agile framework has changed the way business analysts must do their job. Some agile projects even replaced the role of business analysts by the role of the product owner. This replacement has its own drawbacks as it leaves out so much details that are critical to the success of agile projects. Business analysts certainly need to be retrained to be able to contribute to the success of agile projects. Many of the skills that business analysts had for years need to be tuned to the agile mindset. Many other techniques need to be learned and more skills need to be acquired by business analysts to be able to succeed in agile projects.

The instructor draws on his 30+ years of experience working with requirements and user stories in agile and non-agile projects to provide you with all that you need to succeed in agile projects. The course will have a number of workshops where participants can work on real problems.

This course is critical for all members of the agile team including Product Owners, Scrum Masters, Developers, and QA.

Duration:

Although this is meant to be a two- or three-day course, the course is also offer as one-day course. The difference is in the depth of coverage and the number of hands-on workshops.

Participants will learn:

Upon completing this course, participants will:

• Gain a good understanding of the agile mindset and how different it is from the waterfall model
• Gain a good understanding of the elements and roles of the Scrum methodology
• Learn how to participate in collaborative reviews of requirements and user stories
• Learn how to add more details requirement and user stories through scenarios and acceptance criteria
• Understand the difference between requirements and user stories
• Learn how to work with screen prototypes to derive more details
• Learn how user story and requirement traceability works in agile projects

Outline

• Introduction to agile and the agile manifesto
• The Scrum methodology
• Product backlogs
• Working with requirements and Scenarios
• Understanding quality (non-functional) requirements
• Working with User Stories and Acceptance Criteria
• Understanding the limitations of User Stories
• Bringing Traceability back to agile projects
• Working with Wireframes and screen prototypes
• Collaborative reviews for requirements, scenarios, and user stories