Why is Implementing Effective Requirements Practices So Hard?

Slides:



Advertisements
Similar presentations
1 Let the beauty we love be what we do. Dr. Ralph Young.
Advertisements

27-Feb-01 1 Implementing Effective Requirements Practices Presented by Dr. Ralph R. Young Director, Software Engineering Systems and Process Engineering.
 Transferable Skills – The Doctoral Challenge Allan C. Hutchinson August Chengdu.
Chapter 7 CASE Tools and Joint and Rapid Application Development.
Requirements Analysis INCOSE Systems Engineering Boot Camp
Chapter 2 Succeeding as a Systems Analyst
Dr. Ralph R. Young Director of Software Engineering PRC, Inc. (703) Fifth IEEE International Symposium on Requirements Engineering.
Required Skills for IS PM. Contemplative Questions What skills are important for work in IS? What skills are important for work in IS? Do I have these.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
Introduction to Systems Analysis and Design
COLLEGE-READY LEARNER CRITICAL THINKER ADAPTABLE & PRODUCTIVE LEADERRESPONSIBLE DECISION MAKER SKILLED COMMUNICATOR HISD.
The Importance and Value of Process Improvement. Rationale for Process Improvement Establishing an attitude and culture of quality improvement and continuous.
Copyright 2003 by Ralph R. Young Desired Skills and Characteristics of an Effective Requirements Analyst Presentation for The Washington D.C. Software.
Continuation From Chapter From Chapter 1
Describing Methodologies PART II Rapid Application Development*
Software Project Management Introduction to Project Management.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Dr. Ralph R. Young Director of Software Engineering Systems and Process Engineering Northrop Grumman Information Technology (703)
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Problem Identification
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Requirements Engineering: What, Why, Who, When, and How
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 7 CASE Tools and Joint and Rapid Application Development.
1 Dr. Ralph R. Young Director of Software Engineering PRC, Inc. (703) DOORS USER GROUP CONFERENCE Reston, VA September 17,
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Techtrans17b 1 Software Technology Transfer Why don’t organizations use new ideas?
6/6/01 1 Copyright 2001 by Ralph R. Young Effective Requirements Practices Designed to improve individual, project, and organizational effectiveness. Based.
Requirements Gathering: Pragmatic Ways to Meet Real Customer Needs Requirements Gathering: Pragmatic Ways to Meet Real Customer Needs PMI CVC Professional.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Discuss the analytical skills, including systems thinking, needed for a systems analyst to be successful Describe the technical skills required of a systems.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
PROJECT MANAGEMENT Software Engineering CSE
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.
1 Chapter 9 Implementing Six Sigma. Top 8 Reasons for Six Sigma Project Failure 8. The training was not practical. 7. The project was too small for DMAIC.
Introduction to Systems Analysis and Design
Basic Principles of Good Management
Chapter 1 The Systems Development Environment
Business System Development
Instructor: DR. Hussein Reda
Chapter 1 The Systems Development Environment
Information Systems Development
Management Functions.
CASE Tools and Joint and Rapid Application Development
Chapter 1 The Systems Development Environment
The Systems Engineering Context
TechStambha PMP Certification Training
Succeeding as a Systems Analysts
STRATEGIC PLANNING PROCESS
Chapter 1 The Systems Development Environment
Alfonso Bucero, PMP, PMI-RMP, PFMP, PMI Fellow Managing Partner
Interview with Fortum representative
The value of a project-oriented approach to IT and how we do it in IBM
Overview – Guide to Developing Safety Improvement Plan
Chapter 1 The Systems Development Environment
MBI 630: Systems Analysis and Design
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Enterprise Program Management Office
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Requirements Management - I
Teamwork.
Chapter 1 The Systems Development Environment
Systems Development An Overview of Systems Development
Requirements Development in CMMI
Systems Architecture and Engineering
Remaining Agile on Virtual Teams
The Leadership Excellence Series
Presentation transcript:

Why is Implementing Effective Requirements Practices So Hard? Dr. Ralph R. Young ryoungrr@aol.com www.ralphyoung.net Society for Software Quality February 13, 2003

Causes of Problems Surrounding the Implementation of Effective Requirements Practices There are different ideas and opinions as to what the real requirements are. We don’t know what the real requirements are, do we? We initiate other technical work too early—the result: rework (40-50% of costs). There is lacking an effective mechanism to control changes to requirements and new requirements during the development process. There is no documented requirements process, or it’s not used, or it doesn’t support the needs of the project and the customer/users. The customer and project management are anxious to get moving on “the real work.” There are a variety of “people-related problems” (resulting in a lack of effective teamwork). Lack of effective communications. People on the project don’t know what each other are doing. Methods, techniques, tools, mechanisms are not familiar, proven, or effective. There is no zeal for continuous improvement. Management. (Sponsorship, support, being there, being aware, make timely decisions.) Requirements analysts could benefit from more training and knowledge. A project risk management process is not used effectively to identify, analyze, prioritize, and mitigate project risks.

Effective Project Practices Commit to the approach. Establish and utilize a Joint Team to be responsible for the requirements. Define the real customer needs. Use a requirements process and continually improve it. Iterate the system requirements and the system architecture repeatedly. Use a mechanism to maintain project communication between and among all engineering groups throughout the development effort. Select familiar methods and maintain a set of work products that collectively comprise the current requirements specification. Perform requirements verification and validation. Provide an effective mechanism to accommodate changes in requirements during system life cycle development. Perform the development effort using known familiar proven industry, organizational, and project best practices.

Some Characteristics of Effective [Requirements and Quality] Analysts An attitude of continuous improvement and commitment to meet customers real needs. Good listener, communicator, and writer. Commitment to learning, applying, and using improved practices and methods, and to project success. Proactive in engaging co-workers, project management, customers, and users. Expert knowledge of requirements engineering and requirements practices. Ability to estimate the resources and time required to accomplish technical work. Takes responsibility for her/his views, attitudes, relationships, and actions. Maintains focus on keeping the main thing the main thing. Persevering. Maintains a good knowledge of evolving technology and how it can be applied to meet customer needs. Sets achievable goals and meets them. Desires to "make a difference" in his/her professional work. Good facilitation skills. Ability to "think outside the box" to provide creative approaches that might not occur to people who are close to the problem and the legacy system.