Most projects struggle with requirements. Understanding the sources of different types problems with requirements provides insight into avoiding problems later on. This presentation will present three major types of requirements errors (errors of conception, errors of specification, and errors of implementation) and will describe strategies for how to avoid them. Learning Objectives:
- To be able to understand different types of requirements errors
- To be able to recognize problems with requirements
- To be able to apply strategies to avoid requirements errors
Skill Level: Intermediate
|
Kurt Bittner
CTO, Ivar Jacobson Consulting, Americas
Kurt has worked in the software industry for over 25 years in a variety of roles including developer, team leader, architect, project manager, and business leader. He has led agile projects, run a large division of a software development company, survived and thrived in several start-ups, run an acquisition, and worked with clients in a variety of industries including aerospace, finance, energy, and electronics. He was a key contributor to the early development of the Rational Unified Process as well as, more recently, IBM's Jazz project (see www.jazz.net). His experience includes significant work in Banking and Finance, relational database system design and architecting, and consulting and mentoring a wide variety of clients on software development improvement strategies and approaches.
He is the co-author, with Ian Spence (Ivar Jacobson Consulting's Chief Scientist), of two books:
Use-Case Modeling (2002) and Managing Iterative Software Development Projects (2006), as well as many articles, especially in the areas of improving requirements and software development management practices. He has particular interest in assisting organizations and development teams to be more effective in their software practices while not losing sight that developing software should be a fun though highly challenging activity.
|
