| |||||||||||
© 2012 Plannow Technologies, Inc. All Rights Reserved.
| ||||||||||||||
How to Define Business Requirements Through Agile User Stories
| Workshop Overview Every software development project starts with gathering business requirements. How these requirements are documented or expressed have a tremendous influence on the rest of the project. Requirements are referred to as user stories in the Agile environment. The concept of user stories originated in the Agile world, but they are also extremely useful even if you are not planning to use an Agile process. Defining business requirements as user stories is one of the most widely applicable Agile techniques. Learning Objectives In this workshop, we will look at how to identify and write effective requirements through user stories. We will discuss how user role modeling will help you in identifying contextual user stories. During this hands-on workshop you will have the opportunity to practice identifying user roles, eliciting and writing business requirements (user stories) on a case study. Discussion Topics Some of the topics that will be presented include:
|
| Who Should Participate Product owners, business analysts, testers, project managers, product managers, scrumMasters and developers. No prior Agile knowledge is required. Basic knowledge of software engineering is required. Workshop Format The format will consist of lectures to present requirements collection concepts, followed by discussions, role-play and hands-on, real-world case studies that will allow participants to implement the concepts they were just introduced to. At the end of the workshop the participants will have the knowledge to successfully apply the techniques they have learnt in their organization. What Participants Will Receive
|
|