In partnership with Women in Technology International (WITI)
Studies have shown that as many as 4 out of 5 development projects go over time, over budget or don't deliver expected results (The Chaos Report, 1994 Standish Group). With such long odds, it pays to put in the effort upfront to minimize the risk of failure. The question is, how do we achieve this? There is no one perfect method for gathering and analyzing a project's requirements. If there was, we'd all be using it.
This joint International Institute of Business Analysts (IIBA) and Women In Technology International (WITI) event will cover:
• Components of three different types of Requirements • When they are used and why
Whether you are a user providing the information regarding what you want; a Business Analyst gathering requirements or a developer and or tester reading and interpreting the information, this session is for you! Learn about requirements that generate results!"
Combining Agile Technologies for Effective Analysis of Requirements
AgileBill Krebs - Allscripts-Misys
Agile is discipline. Methodologies such as Scrum focus on lightweight yet formal approaches to project management. Understanding the requirements is key to keeping the project on track. User stories are a foundational building block for agile teams. They include acceptance tests to be sure we build the right thing.
But how do we come up with and prioritize these stories? What makes a good (or bad) story? Innovation Games offer techniques to avoid writter's block when developing stories. This talk will show how User Stories, Outside In Design, Innovation Games, and virtual Collaboration come together to create and maintain our feature list.
RSS Feed