When does class start/end?
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
Project failures are often due to poor requirements gathering, analysis and planning. Traditional requirements documents may not contain complete and accurate requirements due to rapidly changing...Read More
Project failures are often due to poor requirements gathering, analysis and planning. Traditional requirements documents may not contain complete and accurate requirements due to rapidly changing business environments. Agile requirements gathering, by moving detailed requirements closer to implementation, allows for rapid response to change. This "User Story Workshop" will show you how to define and manage these requirements effectively as well as demonstrate alternative ways of documenting requirements and managing changes. These alternatives can allow for a less "heavy" process in projects that can benefit from quick changes in direction. This practical workshop provides participants with an understanding of the changing role of the business analyst, the tools and techniques best suited to Agile, and the timing for performing key tasks and events. Explanatory, demonstrations, and practice exercises will provide you with the experience needed to create user stories that meet business needs.
Teams will create User Personas to understand the concept and identify details that make them unique
Teams will practice writing stories using the Roles identified from the User Persona exercise. As a group acceptance criteria will be written, simulating a backlog grooming session.
Individually the group will write an example of a Spike, Non-Functional requirement and a Defect. Focusing on what makes them unique and how best to document the details for development.
Teams will create a list of features, focusing on the evolution of an application and ways in which to build upon a feature over time.
Teams will create Epics for the features identified in the previous exercise, focusing on how to break down the work into valuable slices.
The group will critique stories that have been given to them, learning what to look for when grooming stories (size, unclear, dependencies).
Teams will write stories that relate to the Epics written in the previous exercise. Focusing on the INVEST strategy of story writing and using group feedback to further refine.
The group will be given a sample process map, they will break the process into stories that remain independent and valuable, even if the value varies.
Individually, the group will get to focus on real world examples, getting feedback from the group intermittently, similar to a series of grooming sessions. Ideally bringing these stories back to their own projects.