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 MoreProject 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 training course 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 course is beneficial to all members on an Agile team, but will add the most value for those in a Product Owner role or are a part of the development team and have focus on grooming the product backlog.
This course is perfect for:
Exercise 7: Teams will discuss and document use cases, including alternate pathsand exceptions, for some of their high-priority stories. As a class, we'lldiscuss the relationship between use cases and stories and how they complementeach other.