Topic: RE @ Agile - The future of Requirements Engineering in an agile context.
Dr. Kim Lauenroth is a Ph.D. in Requirements Engineering Board Member of IREB, Germany.
Dr. Kim Lauenroth is Chief Requirements Engineer and leads a competence center for requirements engineering at Adesso AG. He has over 10 years of experience in software and requirements engineering in different domains. He regularly speaks at internal conferences in the topic of RE. Within IREB, he is involved in the development of the advanced level module Elicitation & Consolidation. Dr. Kim Lauenroth received his PhD in the field of requirements engineering from the University of Duisburg-Essen and studied computer science, business administration and psychology at the University of Dortmund.
Topic : The role of the Product Owner in agile and its impact on requirements engineering
Shane Hastie is a MIM, CBAP, ICE-VM Chief Knowledge Engineer and Agile Practice Lead at Software Education.
Shane is a professional trainer and consultant specialising in Agile practices, business analysis, project management, requirements, testing and methodologies for SoftEd in Australia, New Zealand and around the world. Over the last 30+ years he has been a practitioner and leader of developers, testers, trainers, project managers and business analysts; helping teams to deliver results that align with overall business objectives.
He has a Masters in Information Management degree (case study in the implementation of Agile methodology for a global software house), is one of the first CBAP™ (Certified Business Analysis Professional) qualified professionals in the world and is Certified in software testing (International Software Testing Qualifications Board). He also holds the CSM, CSPO and ICE-VM certifications. He is a Board member of the Agile Alliance and a signatory to the Agile Manifesto.
Topic 2: Avoid Scope Creep-Discover the REAL Requirements
There is a simple (though not easy) way to avoid much of the requirements/scope creep which is the main cause of project overruns, which project and requirement engineer ignore as negligible occurrence. Contrary to mistaken conventional wisdom, creep mainly occurs when product/system/software requirements fail to meet the REAL, business requirements usually because developers don't recognize business requirements' importance or how to discover them. In this well-received interactive session based on his 'Discovering REAL Business Requirements for Software Project Success', book, requirements expert Robin Goldsmith reveals the seldom-recognized real reasons creep occurs, introduces how to use the powerful Problem Pyramid™ to guide discovering the REAL requirements, and shows how to document scope in ways that can dramatically reduce creep.
Robin F Goldsmith, JD is President of Needham, MA USA consultancy Go Pro Management, Inc. He works directly with the trains business and system professional on REAL requirements, risk based proactive software, quality assurance and Testing, REAL ROI, metrics, outsourcing, project and process management. Currently President of the software quality group of New England and formerly International Vice President of the Association for systems management and executive editor of the Journal of System Management, Mr. Goldsmith is a subject expert on requirements and testing for Tech Targets, Searchsoftwarequality.com. He is author of the book, Discovering REAL Business Requirements for Software Project Success, and the forthcoming book, Cut Creep--Put Business Back in Business Analysis to Discover REAL Business Requirements for Agile, ATDD, and Other Project Success. Reach him at www.gopromanagement.com or email@example.com
Those of us who have been writing software for a while know that if you don’t get the requirements right, it really doesn’t matter how well you execute the rest of the project. But eliciting, analyzing, specifying, validating, and managing requirements is hard, and not everyone comprehends its criticality This presentation describes seven critical success factors that will go a long way toward making the requirements activities in your organization pay off for the many project stakeholders.
Karl Weigers is a principal consultant with Process Impact, a software process consulting and education company in Portland, Oregon. His interest include requirements engineering, peer reviews, process improvements, metrics and project management. Previously, he spent 18 years at Eastman Kodak company as a research scientist, software developer, software manager and software process and quality improvement leader. Karl received his PhD in organic chemistry from the University of Illinois.
Karl’s most recent book is Software Requirements, 3rd Edition (with Joy Beatty). He’s also the author of the books 'More About Software Requirements', Practical Project Initiation, Peer Reviews in Software, Creating a Software Engineering Culture, and a memoir of life lessons called Pearls from Sand (PearlsFromSand.com). Karl has written nearly 200 articles on software development and management, chemistry and military history. He has served on the editorial board of IEEE software magazine and as a contributing editor for software development magazine. You can reach Karl at Processimpact.com or Karlweigers.com